#StateofHTML

We’ve always told web devs that browsers prioritize what to implement based on developer demand. There is one exception: SVG. SVG is used on >65% of websites. Yet, browsers have been *refusing* to work on SVG, ignoring pressure and pain points from web devs. #StateOfHTML showed SVG as the top content pain point: Tons of work (SVG 2, fill & stroke, and more) has sat unimplemented for years. At this point, in standards circles, we know not to touch SVG with a barge pole. Case that prompted this post, Custom SVG elements. 7y of pressure, a cornucopia of use cases, yet “no implementer interest”: Can someone shed some light on why browsers are so desperate to kill SVG? Because at this point, I refuse to believe this is just a rational business decision based on hard facts. The hard facts are shouting “Fix your damn implementations!” and browsers are going "la-la-la" 🙉🙉🙉

The inaugural #StateOfHTML 2023 Survey has launched! Read my blog post for background: Or take the survey directly:

Doing some preliminary analysis over the #StateOfHTML pain points data and some um, …interesting patterns are emerging 🙃

🔥 I have news! After a 1y hiatus, I’m once again leading this year’s #StateOfHTML survey, thanks to generous funding by Google. ❤️ 🙋🏽‍♀️ Is there is an HTML feature or Web API you're just dying to see progress on? Suggest it and it could be included! Browsers fund these surveys to see what matters to devs — so if others care too, it can really help. E.g. these surveys are the reason we have CSS Nesting. ⌛️ Don’t wait too long to suggest your ideas though; the survey is launching later this month, so time is of the essence!

🚀 The #StateOfHTML 2025 survey is now open! ➡️ Take it now: 💡 Spending time to fill these out is an investment into your craft, as browsers use the results to make prioritization decisions. You don't have to do it in one sitting (or even one device).

After popular demand, we decided to extend the #StateOfHTML survey until Oct 16th. 🥳 Last chance to take it, or finalize your answers if you have already taken it! Maybe you remembered more pain points after taking it? Go back and write them in!

🚨 #StateofHTML 2025 closing in a few days! If you’ve been planning to take it but putting it off, now’s the time:

I got a 380 points knowledge score on this year’s #StateOfHTML survey! I have used 28 features, and knew 20 more, placing me in the top 6% of all respondents. Can you beat my score?

⚠️ Last chance to fill out #StateOfHTML 2025 and get browsers to pay attention to your web platform pain points! After popular demand, the survey closing date has been extended for a few more days so that returning OOO folks get a chance to fill it out too!

Despite leading this year’s #StateOfHTML survey, I procrastinated in typical Lea fashion and submitted my response in the last few hours 😮‍💨 — I had to beg @SachaGreif to leave it open for just a little longer🫣 If you’re like me, here’s the link: We’ll close it and start processing the data when he wakes up tomorrow (it's now night in 🇯🇵) All questions are optional, so even partial responses are useful!

Interesting issue I encountered while implementing a prototype for this optional sentiment chips UI concept for #StateOfHTML The whole row is a <label>, which means clicking anywhere on the row selects the answer. We want to keep that, because Fitts Law.

When looking at results from web development surveys (e.g. #StateofHTML), what are you looking for when looking at the data? What conclusions are you trying to draw?

We are listening and improving the #StateOfHTML survey realtime in response to your feedback! We just switched over to a point-based model for scoring compared to the previous percentage, which some of you felt was unfair as it was not possible to express awareness for 89 out of the 131 features. If you’ve already taken the survey, you can just revisit the finish page and it will show you your score with the new algorithm. For example, here is mine (old one on the right).

The #StateOfHTML 2023 results are finally out! Enjoy insights from 22K responses about the state of the web platform, from HTML and interactivity to #webcomponents, PWAs, and a lot more. This project is a monumental effort from people across the world. We even designed novel data collection UIs to gather the data we needed while minimizing friction, which I plan to write a case study about soon.

Last week, @dawntraoz and @JsfnSchfr were looking at the #StateofJS, #StateofHTML & #StateofCSS reports on Chat as ANY. Let's just say - we were really excited about all this data 😏

On the topic of #StateOfHTML survey design, I’ve been wondering what’s a good way to capture participant background. Today I came up with this quirky prototype! Thoughts? Could it work, or terrible idea? Discussion:

Well I don't think I'm in the top, I'm just an early respondent. 😊 Be sure to participate in #StateOfHTML survey!

The #StateOfHTML survey is out. If you're building for the web, your participation will play a pivotal role in defining the future of the web.

¿Crees saber de HTML? 😂 Te reto a que contestes la encuesta de #StateOfHTML y publiques tu resultado 👇🏽

📣 Announcement! Google is funding me to design a new #StateOfHTML survey, to complement the well-established #StateofJS & #StateofCSS surveys. As a believer in transparency and co-design, I’m opening up the design process to community input: