-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
State of CSS 2023 results #452
Comments
For the browser incompatibilities question, there were 5659 responses. Inlining the results table here, using bold for the ones which aren't already part of Interop 2023:
There were only 239 "Other Answers" which I've pasted in https://gist.github.com/foolip/405d8b401857ba38a54d8da8776d2ff5. It looks like View Transitions is the most common response that isn't already part of the Interop effort. |
Here are the 207 freeform responses for the Missing Features question: And the 122 freeform responses for Other CSS Pain Points: |
To put it on everyone's radar, the State of CSS 2023 results are available. These questions in particular are of interest for prioritizing interop issues:
https://2023.stateofcss.com/en-US/usage/#css_interoperability_features
https://2023.stateofcss.com/en-US/usage/#css_missing_features
https://2023.stateofcss.com/en-US/usage/#css_pain_points
Note that the page says it was a freeform question, but IIRC it was a multi-select question with the option of writing in other answer. Make sure to check the "Other Answers" tab for those.
The text was updated successfully, but these errors were encountered: