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. I remember seeing this a few years ago: https://github.com/WICG/webcomponents/blob/gh-pages/proposal...
    comment by mfe7 · 2022-06-01 · in Show HN: I made React with a faster Virtual DOM
  2. Ah, I didn't realize this wasn't solved -- a quick search turns up: - https://github.com/WICG/webcomponents/issues/788 - https://github.com/w3c/DOM-Parsing/issues/58 - https://github.com/w3ctag/design-reviews/issues/494 -…
    comment by hardwaresofton · 2022-04-04 · in Shoelace: A Web Component Kit
  3. this is called an html module: https://github.com/WICG/webcomponents/blob/gh-pages/proposal...
    comment by replygirl · 2022-03-21 · in CSS's !important was added because of laws about font size for some text
  4. …Extension of builtin elements are much better served with mixins. ... And this entire comment: https://github.com/WICG/webcomponents/issues/509#issuecommen... --- end quote --- So did Safari endorse Web Components? Yes. And they still do.…
    comment by dmitriid · 2022-03-15 · in New WebKit features in Safari 15.4
  5. …remains the "new IE", the problem browser for which developers must find workarounds. (1) e.g. https://github.com/WICG/webcomponents/issues/509 and other forums besides
    comment by inopinatus · 2022-03-15 · in New WebKit features in Safari 15.4
  6. …idea of declarative web components really should happen. There was a strawman proposal a bit back: https://github.com/WICG/webcomponents/blob/gh-pages/proposal...
    comment by rektide · 2021-10-30 · in Why don’t we use HTML to author web components?
  7. …(all, here's one example [1], ugh politics). [0] https://bugs.webkit.org/show_bug.cgi?id=182671 [1] https://github.com/WICG/webcomponents/issues/587#issuecommen...
    comment by krono · 2021-09-29 · in What's New in React 18?
  8. It's being discussed mainly in the WICG web components GitHub repo. There are recent issues in here: https://github.com/WICG/webcomponents/issues
    comment by spankalee · 2021-01-16 · in Show HN: Forgo.js – a 4kb React alternative based on plain JS and DOM APIs
  9. Ballpark guess - less than 5 years. There is the work ongoing on CSS and HTM modules at: https://github.com/WICG/webcomponents/blob/gh-pages/proposal... https://github.com/WICG/webcomponents/blob/gh-pages/proposal...
    comment by lenkite · 2020-12-07 · in Why I Love Tailwind
  10. …, same situation, everyone likes it, only Chrome ships so far) and focusability ( https://github.com/w3c/webcomponents/issues/762 , still figuring out what the solution should be).
    comment by domenicd · 2020-09-30 · in The Failed Promise of Web Components
  11. …versions of the same element. And there has been an open issue for it for three years now: https://github.com/w3c/webcomponents/issues/716 And the "solution" seems to be "let's add more Javascript": https://github.com/justinfagnani/scoped-c…
    comment by dmitriid · 2020-08-07 · in Microsoft Fast Design
  12. Link to proposals: https://github.com/tc39/proposal-import-conditions https://github.com/w3c/webcomponents/blob/gh-pages/proposals...
    comment by dmix · 2020-07-18 · in Ways to make a web component
  13. …and not have default access to APIs like XHR and fetch, or other APIs used for fingerprinting. [1]: https://github.com/w3c/webcomponents/blob/gh-pages/proposals... [2]: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/maste...
    comment by spankalee · 2020-07-09 · in Reddit's website uses DRM for fingerprinting
  14. …primitives to help developers. The current best proposal in this area is Template Instantiation: https://github.com/w3c/webcomponents/blob/gh-pages/proposals... The main idea is that it lets you mark up a <template> with references that…
    comment by spankalee · 2020-03-30 · in Open UI
  15. …on that. This is HTML thing - it is not a library specific problem. It might get solved eventually https://github.com/w3c/webcomponents/issues/716 . I come from python world where you have same restriction for all packages so it never…
    comment by ergo14 · 2020-02-15 · in ING open-sources Lion, a library of accessible and flexible Web Components
  16. …They are called custom elements. https://html.spec.whatwg.org/multipage/custom-elements.html#... https://github.com/w3c/webcomponents/ https://developer.mozilla.org/en-US/docs/Web/Web_Components/...
    comment by nidificate · 2019-10-30 · in When XML Beats JSON: UI Layouts
  17. …some very good ideas to the W3C/WHATWG groups (like their Template Instantiation proposal [0]) [0] https://github.com/w3c/webcomponents/blob/gh-pages/proposals...
    comment by no_wizard · 2019-08-21 · in The Browser Monopoly
  18. Here's a link that actually shows some code and I think explains what this is about: https://github.com/w3c/webcomponents/blob/gh-pages/proposals... It's nice to see Microsoft pushing this forward as it's pretty neat, but we'll need to see…
    comment by rubyn00bie · 2019-08-12 · in Intent to Implement: CSS Modules V1
  19. …. [1] https://dev.to/dan_abramov/comment/6kh1 [2] https://w3c.github.io/ServiceWorker/ [3] https://github.com/w3c/webcomponents/blob/gh-pages/proposals... [4] https://github.com/w3c/webcomponents/issues/747
    comment by dmitriid · 2019-08-12 · in Faster AMP on the Origin: AMP and SSR
  20. …very much is using the platform. CSS Modules will make it possible to directly import a Stylesheet: https://github.com/w3c/webcomponents/issues/759
    comment by spankalee · 2019-06-20 · in Why I don't use web components
  21. It's being worked on: https://github.com/w3c/webcomponents/issues/716 The fundamental difference here is that HTML needs to know what class to instantiate when it sees a tag. Supplying that unlocks a lot of power, like custom elements in…
    comment by spankalee · 2019-06-20 · in Why I don't use web components
  22. …on GitHub which in my opinion is going nowhere because TI is viewed as unquestionable good https://github.com/w3c/webcomponents/issues/704
    comment by dmitriid · 2019-05-19 · in Virtual DOM is pure overhead (2018)
  23. …docs, blog…) and you can’t pre-render them, because there is no declarative Shadow DOM element https://github.com/w3c/webcomponents/blob/gh-pages/proposals... (rejected https://github.com/whatwg/dom/issues/510 ). Yeah, you can pre-render…
    comment by JackuB · 2019-04-12 · in Web Components could replace frontend frameworks?
  24. You might be interested in this: https://github.com/w3c/webcomponents/blob/gh-pages/proposals...
    comment by robrez · 2019-04-12 · in Web Components could replace frontend frameworks?
  25. …are the spiritual successor to HTML Imports that work with the standard JS module loading system: https://github.com/w3c/webcomponents/issues/645
    comment by spankalee · 2018-11-16 · in The Power of Web Components
  26. …that showcase some conveniences to deal with templates in components, could be good, could be bad. https://github.com/w3c/webcomponents/blob/gh-pages/proposals... Most communication I solve by custom event dispatching or attribute…
    comment by holmberd · 2018-06-13 · in Making Web Components Work
  27. …capabilities of Web Component frameworks or React, or Angular, or Vue (hell, of even Snabbdom). [1] https://github.com/w3c/webcomponents/blob/gh-pages/proposals...
    comment by dmitriid · 2018-06-13 · in Making Web Components Work
  28. See shadow dom section in here: https://github.com/w3c/webcomponents/ which specified most of docs are maintained in here: https://dom.spec.whatwg.org/ And as for what it is, you know how a given web page has global css/query selector…
    comment by captain_crabs · 2018-05-28 · in Shadow DOM enabled in Firefox nightly
  29. …in a standard form, follow the work being done on HTML modules and Declarative Custom Elements: https://github.com/w3c/webcomponents/blob/gh-pages/proposals... Together those will mean UI components without any JavaScript, that can depend…
    comment by spankalee · 2018-05-03 · in Show HN: LayerJS – A simple UI composition and navigation library
  30. …in the standard). [1] There is no way to have custom elements include data in form submissions: https://github.com/w3c/webcomponents/issues/187 and the solution is "to replicate the behaviour of form elements (which requires you to also to…
    comment by dmitriid · 2017-11-04 · in Show HN: React patterns, techniques, tips and tricks
  31. Another example of why we need HTML Modules: https://github.com/w3c/webcomponents/issues/645
    comment by spankalee · 2017-10-05 · in Show HN: Single-file components for React
  32. …as being implemented in custom elements v2, but is closed to see what frameworks come up with: https://github.com/w3c/webcomponents/issues/136 . This is totally something that could be done with Skate, though.
    comment by treshugart · 2016-11-03 · in Show HN: SkateJS – a cross framework web components based library
  33. …on a revision to that spec to build it on top of the ES2015 module loader so it's not contentious ( https://github.com/w3c/webcomponents/blob/gh-pages/proposals... ). But HTML Imports is not a requirement for Web Components, the big win is…
    comment by robdodson · 2016-03-02 · in Custom Elements Coming to WebKit
  34. …up to this "spec's" vision. [1] https://github.com/OscarGodson/HTML6/commit/7d58a98b30fe473d... [2] https://github.com/w3c/webcomponents/commit/c60060999073e181...
    comment by BrandonSmith · 2014-12-02 · in HTML6 Concept