Philip Jägenstedt

I think this applies to https://2023.stateofcss.com/en-US/usage/#css_missing_features as well, and possibly other questions that were changed from freeform to multiple choice in 2023.

For the "what's missing from CSS" question, since we know from last year roughly what the areas are, can we make it a "pick 3 plus write in if other"...

> Would it be possible to ask about interoperability in this survey? I.e. an option for "would use a property if it was supported cross browser" I love this suggestion,...

> Also as general feedback, we try to stay away from open-ended, qualitative questions ("what performance issues do you run into?") because we can't really do much with the resulting...

> > For the "what's missing from CSS" question, since we know from last year roughly what the areas are, can we make it a "pick 3 plus write in...

@SachaG for "what areas of CSS do you struggle with the most with?" we have some precedent for this in [Layout/styling feature that cause issues](https://insights.developer.mozilla.org/reports/mdn-browser-compatibility-report-2020.html#survey-layout-styling-feature-that-cause-issues) from the MDN browser compat...

In the survey preview, I spot some odd capitalization of CSS properties when used as headings/titles, like "Position: sticky", "Object-fit" and "Clip-path". If that's a choice that seems OK, but...

I also have a humble proposal for alignment with the MDN Developer Needs Assessment on one question, which is an overall satisfaction question. The draft already has Overall Happiness questions...

> > To my proposal. Asking about overall satisfaction with the web early (to avoid priming) in the survey would be great for comparing across this survey and MDN's. It's...

I just took the survey myself and could see how my suggested questions for happiness with the web and CSS and large turned out, thanks @SachaG! I do want to...