#StateOfHTML

⚠️ 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!

🚀 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).

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?

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!

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

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.

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.

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?

text-wrap: balance and friends are great, but what I often need is the <br> version of ­ “If you need a line break, here's a good place, but if not, nvm!” cc @fantasai @kojiishi

@LeaVerou @luke_warlow @fantasai @kojiishi Alternative, as a horrible hack, you can replace all spaces in a paragraph with   except for the line-break points (or put <wbr> there). Try not to 🤮 too much when looking at the code 😂

Haha I also wondered about that. It's not quite the same, since the browser *would* be able to break elsewhere, but only if breaking within a shy line break was not an option. E.g. consider this description from #StateofHTML (which inspired this): I want a way to say "If you need to wrap this into two lines, break right before 'Syntax'. If you need to wrap into 3+ lines, feel free to insert additional breaks."

This is lovely but individual component authors should not need to figure this on their own. Menus and submenus are such a fundamental GUI component that it should be native to the web platform like it is on every other platform…

Implemented safe triangles to improve submenu selection in @shoelace_style today.

@LeaVerou I never really got why the web did not add more of these basic elements. It would make development of small apps so much quicker. Things like datatables with filtering & searching. Some basic charts,… Adobe Flex was so nice to develop in because it was all in the platform.

@pbriers Totally agreed. I hope you’ve entered this in the relevant #StateOfHTML questions!

I don't know how I did it but: I got a 950% knowledge score on this year's #StateOfHTML survey! Take the survey here:

🔥 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!

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" 🙉🙉🙉

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

I got a 315 pts knowledge score on this year’s #StateOfHTML survey! I have used 21% (28/131) features, and knew 17% (7/42) more. Can you beat my score? 😅

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

I got a 660 pts knowledge score on this year’s #StateOfHTML survey! I have used 46% (60/131) features, and knew 29% (12/42) more. Can you beat my score?

🔥 New blog post! 🔥 If you’ve ever written a survey, you have stumbled on this dilemma: Brackets or keyboard input for numerical answers? Here I outline my thought process for #StateOfHTML, including a framework for making decisions of this type:

I got a 790 pts knowledge score on this year’s #StateOfHTML survey! I have used 56% (74/131) features, and knew 24% (10/42) more. Can you beat my score?

J'ai obtenu un score de connaissance de 1010pts sur le questionnaire #StateOfHTML de cette année! Pour y participer, rendez-vous ici: (ndlr: quand avoir déjà intégré la balise <applet> ou <marquee> rapporte des points)