Hacker GitHub

← All repos

WICG/webcomponents

View on GitHub ↗ ★ 4,492 HTML

Web Components specifications

96 mentions on Hacker News by 53 people: 12 stories, 84 comments · first 2014-12-02 · latest 2026-08-02

Mentions per year 96 mentions · busiest year 2023 (18)
20082026
AllStoriesComments NewestTopOldest
  1. …element registries proposal covers some of the use cases where global elements are problematic https://github.com/WICG/webcomponents/blob/gh-pages/proposal...
    comment by cube00 · 2026-08-02 · in Progressive Web Components
  2. …Oops, still cannot be a custom form submit button. Here's a 7-year old still unresolved issue: https://github.com/WICG/webcomponents/issues/814 For frameworks: Framework authors have to patch all thise holes on their own. Because unlike…
    comment by troupo · 2026-08-01 · in Progressive Web Components
  3. …not evil/incompetent board executives twirling their mustaches as they deliberately break the web: https://github.com/WICG/webcomponents/issues/509#issuecommen...
    comment by chuckadams · 2026-07-16 · in If you want to create a button from scratch, you must first create the universe
  4. …to allow Passkey support in forms without having to write javascript as an end-user. I ran into https://github.com/WICG/webcomponents/issues/814 As long as this is not fixed I can't take Web Components seriously.
    comment by arianvanp · 2026-02-20 · in Web Components: The Framework-Free Renaissance
  5. There's a long standing standards issue for this: https://github.com/WICG/webcomponents/issues/909 While you can easily turn rendering to shadow DOM off on a per-component basis, that removes the ability to use slots. It only really works…
    comment by spankalee · 2025-12-29 · in You can make up HTML tags
  6. …- signals, which is currently Stage 1 https://github.com/tc39/proposal-signals - And this proposal: https://github.com/WICG/webcomponents/issues/1069 which is basically lit-html in the browser
    comment by brazukadev · 2025-12-15 · in JSDoc is TypeScript
  7. …"form associated custom elements cannot be a submit button" issue was opened 6 years ago, in 2019: https://github.com/WICG/webcomponents/issues/814 In 2022 web component group report mentions it in passing:…
    comment by troupo · 2025-09-04 · in Lit: a library for building fast, lightweight web components
  8. …function as submit buttons: https://w3c.github.io/webcomponents-cg/2022.html#form-associ... and https://github.com/WICG/webcomponents/issues/814 And that's before we get into how they break many other things. Like the fact (that you…
    comment by troupo · 2025-09-04 · in <template>: The Content Template element
  9. …browser vendors that this is needed, but I'm holding out hope that it makes progress soon. [1]: https://github.com/WICG/webcomponents/issues/909
    comment by jfagnani · 2025-09-03 · in Lit: a library for building fast, lightweight web components
  10. …safe to evaluate (their templates might expressive enough to potentially allow attacks). [1]: https://github.com/WICG/webcomponents/issues/645 [2]: https://heximal.dev/ (Sorry the site is messed up on mobile. I need to fix it!)
    comment by jfagnani · 2025-09-02 · in <template>: The Content Template element
  11. …they want it to contain zero template engines. The funny thing? No, they want to create a new one: https://github.com/WICG/webcomponents/issues/1069
    comment by troupo · 2025-08-20 · in "Remove mentions of XSLT from the html spec"
  12. …Form Associated Controls: it's not one spec. It's a bunch of specs fixing idiotic issues like this: https://github.com/WICG/webcomponents/issues/814 Note: easily half of these only exist because of web components and for web components.…
    comment by troupo · 2025-06-28 · in The time is right for a DOM templating API
  13. …Justin Fangnani etc.). They did end up proposing declarative template instantiation in 2017: https://github.com/WICG/webcomponents/blob/gh-pages/proposal... but that mostly went nowhere
    comment by troupo · 2025-06-27 · in The time is right for a DOM templating API
  14. …frame the problem in terms of a "template api", centered around "binding" variables, and what not. https://github.com/WICG/webcomponents/issues/1069 My proposal only adds one native function with nothing else: no new data types, no new…
    comment by hsn915 · 2025-06-27 · in The time is right for a DOM templating API
  15. https://github.com/WICG/webcomponents/issues/1069
    comment by exclipy · 2025-06-26 · in The time is right for a DOM templating API
  16. …@scope will provide this. [1]: https://github.com/css-modules/css-modules/blob/master/docs/... [2]: https://github.com/WICG/webcomponents/blob/gh-pages/proposal...
    comment by recursive · 2025-03-02 · in Knowing CSS is mastery to front end development
  17. …See #331 for details. > We don't have a plan to support an arbitrary selector for ::slotted. — https://github.com/WICG/webcomponents/issues/594#issuecommen... > “Web components” aren’t really a thing This is an empty nitpick. The people…
    comment by JimDabell · 2025-02-21 · in Customizable HTML Select
  18. …that doesn't have the downsides of the original spec and enables new use cases discovered since: https://github.com/WICG/webcomponents/issues/1029 Nothing with customizable built-ins would give you what the original commenter asked for
    comment by troupo · 2025-02-21 · in Customizable HTML Select
  19. …for the web platform. Then there's a direct line to built-in declarative reactive templating: https://github.com/WICG/webcomponents/issues/1069
    comment by spankalee · 2025-02-05 · in Chrome 133 Supports DOM State-Preserving Move with moveBefore()
  20. what you described is lit-html, which might find its way to the browser: https://github.com/WICG/webcomponents/issues/1069
    comment by meiraleal · 2024-12-02 · in If not React, then what?
  21. There is a proposal for JavaScript-based HTML templates: https://github.com/WICG/webcomponents/issues/1069
    comment by spankalee · 2024-11-30 · in If not React, then what?
  22. …a close-to-the-metal solution for templating and data binding in HTML/JS I'm hoping for this one: https://github.com/WICG/webcomponents/issues/1069
    comment by meiraleal · 2024-10-02 · in TinyJS – Shorten JavaScript QuerySelect with $ and $$
  23. …around (e.g., Signals proposal [2]), so we can go back to testing new ideas on top of that. [1] https://github.com/WICG/webcomponents/blob/gh-pages/proposal... [2] https://github.com/tc39/proposal-signals
    comment by hasanhaja · 2024-09-30 · in Web components are okay
  24. …browser APIs. We should make it part of the webcomponents spec! Which is a work in progress: https://github.com/WICG/webcomponents/issues/1069
    comment by meiraleal · 2024-09-29 · in Web components are okay
  25. …for HTML templating in JS since then. But maybe we can revive the general idea with a modern take: https://github.com/WICG/webcomponents/issues/1069
    comment by spankalee · 2024-08-16 · in VanillaJSX.com
  26. …this is it: Proposal: Custom attributes for all elements, enhancements for more complex use cases https://github.com/WICG/webcomponents/issues/1029 Searching for "dash" does bring up a thread of discussion around whether to require dashes…
    comment by lioeters · 2024-07-17 · in CSS Classes Considered Harmful
  27. …There's also an idea for isolated web components to solve this in the platform: https://github.com/WICG/webcomponents/issues/1002
    comment by spankalee · 2024-07-07 · in Show HN: Execute JavaScript in a WebAssembly QuickJS sandbox
  28. You're absolutely correct. (For reference, here's a long discussion in an issue: https://github.com/WICG/webcomponents/issues/814 )
    comment by troupo · 2024-05-09 · in Facebook just updated its relationship status with Web Components
  29. …we find folks rarely (if ever) collide, the same as ObjC. (Not that things couldn't be better: https://github.com/WICG/webcomponents/blob/gh-pages/proposal... )
    comment by esprehn · 2024-05-08 · in Facebook just updated its relationship status with Web Components
  30. …worth, there is discussion of an “open-stylable” shadow DOM mode that addresses those concerns: https://github.com/WICG/webcomponents/issues/909
    comment by jakelazaroff · 2023-11-27 · in Web Components Eliminate JavaScript Framework Lock-In
  31. …changes at once during the upgrade, unless the draft about scoping web elements became standard https://github.com/WICG/webcomponents/blob/gh-pages/proposal... )
    comment by riquito · 2023-11-27 · in Web Components Eliminate JavaScript Framework Lock-In
  32. …which may interest you. It's called the DOM Parts proposal and you can find info on it here: https://github.com/WICG/webcomponents/blob/gh-pages/proposal...
    comment by djrenren · 2023-11-27 · in Web Components Eliminate JavaScript Framework Lock-In
  33. …a lot of bureaucracy involved in getting HTML Modules out the door since its been eight years. https://github.com/WICG/webcomponents/blob/gh-pages/proposal...
    comment by jnellis · 2023-11-13 · in HTML Web Components
  34. …in forms is still an unsolved problem: > Form-associated custom elements: being a submit button https://github.com/WICG/webcomponents/issues/814 opened 4 years ago and representatives of major browsers still don't have an answer
    comment by morbicer · 2023-10-25 · in Web components will outlive JavaScript frameworks
  35. …global stylesheets. Feedback and support of the need for something like this would help a lot: https://github.com/WICG/webcomponents/issues/909
    comment by spankalee · 2023-10-10 · in Lit 3.0
  36. …completely. Imho this isn't solved anywhere and makes the web components no-go for design systems. https://github.com/WICG/webcomponents/issues/814 I also find baffling that there is _zero_ information about forms in the Lit3.0…
    comment by morbicer · 2023-10-10 · in Lit 3.0
  37. …custom button won't be able to submit your form, sorry, it's a 4-year old issue with no solution: https://github.com/WICG/webcomponents/issues/814 And all that despite the fact that there are already a dozen specs covering web components,…
    comment by troupo · 2023-08-17 · in Things you forgot (or never knew) because of React
  38. …or still have unresolved issues like "custom button cannot submit a form": https://github.com/WICG/webcomponents/issues/814 > but at least jQuery helped shape modern standards. Has anything good come from React for the platform? It c
    comment by troupo · 2023-08-16 · in Things you forgot (or never knew) because of React
  39. …come to expect. It’s still a weird imperative API with no rendering or data binding primitives [0]: https://github.com/WICG/webcomponents/blob/gh-pages/proposal...
    comment by no_wizard · 2023-08-03 · in If Web Components are so great, why am I not using them?
  40. …of an equivalent alternative. (and this is something a polyfill can only partially bridge) [1] https://github.com/WICG/webcomponents/issues/509#issuecommen... [2] https://bugs.webkit.org/show_bug.cgi?id=182671 [3]…
    comment by inopinatus · 2023-08-02 · in If Web Components are so great, why am I not using them?
  41. …components. Note that Safari has opposed subclassing built-in components since the very beginning: https://github.com/WICG/webcomponents/issues/509#issuecommen... Just a few of the reasons: https://github.com/WICG/webcomponents/issues/509#i…
    comment by troupo · 2023-07-21 · in Lit: Simple, fast web components
  42. …load the HTML into the JS module graph and JS can't do that yet, though there is a proposal for it: https://github.com/WICG/webcomponents/blob/gh-pages/proposal... Template in HTML also have the problem of the data not being in scope as it…
    comment by spankalee · 2023-05-15 · in Building a front end framework – Reactivity, composability with no dependencies
  43. A new proposal sketch for isolated web components: https://github.com/WICG/webcomponents/issues/1002
    comment by spankalee · 2023-04-20 · in Sandboxing JavaScript Code
  44. …up are both semi-interesting... but i think are also very due for a longer treatment/write-up. https://github.com/WICG/webcomponents/issues/986#issuecommen...
    comment by rektide · 2023-03-01 · in The point of Web Components was modularity and encapsulation
  45. …Some form of declarative CSS module scripts would help a lot. A feature request for that here: https://github.com/WICG/webcomponents/issues/939
    comment by spankalee · 2023-02-13 · in Declarative Shadow DOM
  46. …to use two different version of your own `my-button`... This is the proposal for scoped elements: https://github.com/WICG/webcomponents/blob/gh-pages/proposal...
    comment by riquito · 2023-02-13 · in Declarative Shadow DOM
  47. …Can we please finally deliver on something people have been asking for since the mid 2000s? [0]: https://github.com/WICG/webcomponents/blob/gh-pages/proposal...
    comment by no_wizard · 2023-02-13 · in Declarative Shadow DOM
  48. In the past I've seen this one: https://github.com/WICG/webcomponents/blob/gh-pages/proposal... Perhaps there are more recent versions. I liked the spirit of the proposal, but never studied it.
    comment by twsted · 2022-10-05 · in Templating in HTML
  49. …assertions and CSS and JSON modules landing [2], HTML modules are probably not far behind. [1]: https://github.com/WICG/webcomponents/blob/gh-pages/proposal... [2]: https://web.dev/css-module-scripts/
    comment by spankalee · 2022-10-05 · in Templating in HTML
  50. I believe this is the current iteration: https://github.com/WICG/webcomponents/blob/gh-pages/proposal... You can learn more of the history here: https://www.w3.org/2020/10/TPAC/parts_and_template_instantia...…
    comment by esprehn · 2022-06-01 · in Show HN: I made React with a faster Virtual DOM