Skip to content

Usage

How you use HTML.

Browser 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.

Which existing HTML features or browser APIs are you unable to use because of browser differences or lack of support?
Freeform
Multiple
Top pain point topics corresponding to specific web platform features.

View:

Items tagged “features”
0%
20%
40%
60%
80%
100%
01
02
-1
03
04
05
06
-1
07
08
09
10
+5
0%
20%
40%
60%
80%
100%

Limited 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.
Which existing HTML features or browser APIs are you unable to use for other reasons (and why)?
Freeform
Multiple
Top pain point topics corresponding to specific web platform features.

View:

Items tagged “features”
0%
20%
40%
60%
80%
100%
01
<input type="date">
+1
02
<select>
-1
03
+1
04
05
+2
06
<select multiple>
07
08
09
<input type="color">
+2
10
<input type="datetime-local">
0%
20%
40%
60%
80%
100%

Missing Elements

We still want native datatables, with tabs coming in a close second.
If you could add new elements to HTML, what would they be?
Multiple
Limited
4
0%
20%
40%
60%
80%
100%
01
Datatable
02
Tabs
+1
03
Combobox/autocomplete
-1
04
Switch/toggle
+2
05
Rich text editor
06
Sortable drag-and-drop list
+2
07
Dropdown menu
-3
08
HTML include
-1
09
Skeleton UI/loading placeholder
10
Context menu/right-click menu
0%
20%
40%
60%
80%
100%

Styling Issues

These rankings mainly confirm findings already seen in other questions: styling continues to be a big issue, especially when it comes to form elements. And at a time when CSS itself is making progress at an unprecented rate, not being able to leverage all this power when it comes to some of the most common parts of any given web UI is certainly frustrating.
Which elements do you struggle the most to style or visually customize?
Multiple
Limited
3
0%
20%
40%
60%
80%
100%
01
<select>
02
<input type="date">
03
<select multiple>
04
05
<input type="time">
+2
06
Validation errors
-1
07
+1
08
<input type="range">
+1
09
-3
10
+4
0%
20%
40%
60%
80%
100%

Progressive 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.

In your typical work context, how important is it that the websites or web apps you build be able to function without JavaScript?
0%
20%
40%
60%
80%
100%
1
Not a concern
2
Low priority
3
High priority
4
Required
0%
20%
40%
60%
80%
100%

HTML/CSS vs JS/TS Balance

Our codebases still contain a lot of JavaScript (or TypeScript). But this could change, as browser expand their native capabilities to let HTML and CSS take over some of the jobs JavaScript is currently tasked with.
How do you divide your time between writing HTML/CSS and JavaScript (or TypeScript) code?
0%
20%
40%
60%
80%
100%
1
100% HTML/CSS
2
12.5%
3
25%
4
37.5%
5
50%–50%
6
62.5%
7
75%
8
87.5%
9
100% JS
0%
20%
40%
60%
80%
100%
💡
Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%.

AI 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%!

What proportion of the code you produce is AI-generated?
0%
20%
40%
60%
80%
100%
1
0% AI
2
12.5%
3
25%
4
37.5%
5
50%
6
62.5%
7
75%
8
87.5%
9
100% AI
0%
20%
40%
60%
80%
100%

Browser AI APIs

Having the ability to avoid slow API calls and get AI features right in your browser is certainly intruiging, but at this point the appeal is still limited.
What AI APIs would you most like to see supported natively in browsers?
Multiple
Limited
3
0%
20%
40%
60%
80%
100%
01
Translation
02
Speech recognition
03
🚫 None
04
Caption generation
05
Language detection
06
Summarization
07
Computer vision
08
Speech generation
09
Text generation
10
Sentiment analysis
11
Image generation
12
Other Answers
0%
20%
40%
60%
80%
100%

Other Pain Points

While most respondents were already able to share their frustrations throughout the rest of the survey, the lack of native HTML includes or templating is something that was cited again here by a few people.
Any other pain points around using HTML and related technologies?
Freeform
Multiple
Top pain point topics overall.

View:

Items that are not one of “limitations”
0%
20%
40%
60%
80%
100%
1
Content
+2
2
Browser vendor issues
-2
3
Ecosystem issues
+4
0%
20%
40%
60%
80%
100%

Recommended Resources

Frontend Masters

Frontend Masters

Advance Your Skills with In-Depth, Modern Front-End Engineering Courses
Sponsored content from our partners. Learn more.