Lea Verou, PhDJul 8, 2025

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

⌛️ The survey is launching later this month, so time is of the essence!

https://lea.verou.me/blog/2025/design-state-of-html/

Influence the State of HTML 2025 Survey! • Lea Verou

Show threadwestbrook

@leaverou These all power HTML in some way or other...

- Scoped Custom Element Registries
- Reference Target API
- elementInternals.type https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ElementInternalsType/explainer.md
- Declarative CSS Modules and the adoptedstylesheets attribute https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ShadowDOM/explainer.md
- Declarative Partial Updates https://github.com/WICG/declarative-partial-updates
- DOM Parts
- Platform based windowing/virtualization
- <tabs>

I've got lots more for CSS/JS if you get signed up for those.

Good luck with the survey!

#webComponents #webComponentsCG #webDev

MSEdgeExplainers/ElementInternalsType/explainer.md at main · MicrosoftEdge/MSEdgeExplainers

Home for explainer documents originated by the Microsoft Edge team - MicrosoftEdge/MSEdgeExplainers

GitHub
Jul 9, 2025 at 12:56amWeb
Show threadBenny Powers 🇮🇱🦁Jul 9, 2025
@westbrook @leaverou i want to know if and why/why not respondents use declarative shadow dom

i want to know if respondents are interested in declarative custom elements

i'm pessimistic that the results from any State of survey will be truly representative, however
Show threadLea Verou, PhDJul 9, 2025

@westbrook Oh absolutely, anything web components related is entirely within scope.

re:<tabs> are you thinking of a specific proposal?

Show threadwestbrookJul 9, 2025
@leaverou I haven't specifically kept up on <tabs> and the like to know to know if there's one worth pursuing, so maybe that's a proxy bullet for adding more elements natively to the browser. IIUC, that requires more flexibly in the parser which would open the door for more and more new elements, which is a win for everyone!!!
Show threadLukeJul 9, 2025
@westbrook @leaverou Tabs shouldn't need a parser change we can add new elements relatively easily. It's changing existing weird ones that is tricky (recent select changes). Tricky bit with tabs is getting people to agree what is a tab.