Making & using web components.
Link to sectionWeb Components Features
Web Components Features
Once again we see declarative solutions prevailing, with declarative custom elements topping the sentiment chart.
Which of the following web component features have you used?
Group by:
Sort by:
1
Web Components
2
Web Components
3
Web Components
4
Web Components
5
Web Components
6
Web Components
7
Web Components
Experience
- <span aria-hidden="true">🤓</span> Used it: Respondents who have used an item.
- <span aria-hidden="true">👀</span> Heard of it: Respondents who have heard about an item, but haven't used it.
- <span aria-hidden="true">🤷</span> Never heard of it: Respondents who have never heard about an item.
Sentiment
- Positive: Respondents who are interested in learning more about a technology; or are willing to use it again.
- Neutral: Responents who did not indicate any sentiment about a technology.
- Negative: Respondents who are not interested in learning more about a technology; or have used it and had a negative experience.
Link to sectionWeb Components Pain Points
Web Components Pain Points
We know that extending built-in elements is a long requested feature, and these results validate it, as it is the top concrete pain point topic here (after the more abstract ones around complexity, reliance on JS, and accessibility).
What are your biggest pain points around creating or using web components?
(freeform question)
Multiple
Top pain point topics overall.
View:
Link to sectionRecommended Resources
Recommended Resources
Vanilla JS: You Might Not Need a Framework
See how you can build rich web apps and websites without depending on libraries or frameworks, using only the core JavaScript language.
Thanks to our partners for supporting us! Learn more.