webcomponents-cg
webcomponents-cg copied to clipboard
w3c
Web Components community group
Adds shell sections for all of the APIs we've discussed so far for this year's report.
Sections we likely need: * Abstract * Introduction * Impact * Prioritization methodology * Cross-cutting Themes For impact we'd like to highlight the large and growing web component usage across...
Now that both Mozilla and WebKit have standards position repos, and more recent specs have been implemented by multiple browsers, I think it would be useful to expand the **status**...
# Declarative custom elements - teaser Not a proposal. Here we could outline the purpose and goals. WIGC proposal would follow. ## Description Defines the convention of defining the [custom...
Link to initial WCCG discussion issue. 
Now that all browsers support complex CSS selectors inside of `:not()`, what prevents the same within `::slotted()` or `:host()`? Browser announcements for reference: - https://webkit.org/blog/3615/css-selectors-inside-selectors-discover-matches-not-and-nth-child/ - https://hacks.mozilla.org/2020/12/and-now-for-firefox-84/ - https://blog.chromium.org/2020/12/chrome-88-digital-goods-lighting.html Naively,...
Perhaps this is trivial but I think having an available logo for Web Components would be helpful for developers who want to reference Web Components on websites, in documentation, etc....
## Overview As a nod to the corresponding survey's for [JS](https://stateofjs.com/) and [CSS](https://stateofcss.com/) respectively, I wanted to open this issue to start a dialog around the value of having some...
Declarative custom elements should be sketched out as a way to verify that other specs that it depends on are suitable to use for it. This includes things like template...
Accessibility is an easy nit to pick when discussing the potential usage of web components, and particularly shadow DOM, in a project. While shadow DOM is certainly not a requirement...