Link to sectionBrowser Interoperability
Customizable select is nearing the finish line, and developers can feel it, with only Firefox lacking support for the long-awaited feature.
Meanwhile, with the Popover API now being supported in all major browsers, we're the number of developers citing browser support as an obstacle to its adoption drop, as it should.
View:
Link to sectionLimited Functionality
<select> scored 10% lower compared to last year, presumably due to the progress made on making it easier to style and customize. Which lets date inputs take the dubious honor of taking the lead as the feature with the most impactful limitations.View:
Link to sectionMissing Elements
Link to sectionStyling Issues
Link to sectionProgressive Enhancement
Progressive enhancement has long been adopted as a key best practice of our industry, but as with many well-intentioned principles there's often a large gap between theory and practice.
In this case, a full 43% of respondents do not concern themselves with making their apps or sites work without JavaScript. While on the other end of the spectrum, it's a requirement for only 4%.
Which is a shame, as considering progressive enhancement a “high priority” was also correlated with employing more accessibility techniques.
Link to sectionHTML/CSS vs JS/TS Balance
Link to sectionAI Code Generation
It's interesting to compare how different segments of the web developer population score when it comes to AI usage.
State of Devs respondents scored a median of 63% of their code being AI-generated, quite a bit higher than the 50% seen here. Meanwhile, when it comes to CSS code more specifically, the median was way lower at only 13%!
