WICG/webcomponents issues and pull requests

#966 - TPAC 2022 Web Components Meeting(s)

Issue - State: closed - Opened by mfreed7 about 2 years ago - 13 comments

#966 - TPAC 2022 Web Components Meeting(s)

Issue - State: closed - Opened by mfreed7 about 2 years ago - 13 comments

#962 - [element-internals] How to get internals in base class and subclass, without leaking it to public

Issue - State: closed - Opened by trusktr about 2 years ago - 17 comments
Labels: custom-elements, question

#962 - [element-internals] How to get internals in base class and subclass, without leaking it to public

Issue - State: closed - Opened by trusktr about 2 years ago - 17 comments
Labels: custom-elements, question

#956 - Place to chat about Web Components standardization

Issue - State: open - Opened by annevk over 2 years ago - 4 comments

#944 - TPAC 2021 Web Components Meeting

Issue - State: closed - Opened by mfreed7 almost 3 years ago - 8 comments

#943 - css-modules: fix typo

Pull Request - State: closed - Opened by songhn233 almost 3 years ago

#943 - css-modules: fix typo

Pull Request - State: closed - Opened by songhn233 almost 3 years ago

#939 - Declarative CSS Module Scripts

Issue - State: open - Opened by justinfagnani about 3 years ago - 26 comments

#939 - Declarative CSS Module Scripts

Issue - State: open - Opened by justinfagnani about 3 years ago - 26 comments

#931 - Update CSS modules explainer to include addition of import assertions

Pull Request - State: closed - Opened by dandclark over 3 years ago - 5 comments

#928 - State of all of the proposals.

Issue - State: closed - Opened by jogibear9988 over 3 years ago - 1 comment

#928 - State of all of the proposals.

Issue - State: closed - Opened by jogibear9988 over 3 years ago - 1 comment

#923 - [scoped-registries] Element upgrade ordering

Issue - State: open - Opened by justinfagnani over 3 years ago - 21 comments

#923 - [scoped-registries] Element upgrade ordering

Issue - State: open - Opened by justinfagnani over 3 years ago - 21 comments

#918 - CSS Shadow Parts Selector ::part() does not work in combination with :disabled pseudo-class in Chrome

Issue - State: closed - Opened by Dev89787 over 3 years ago - 4 comments
Labels: shadow-dom, question, css

#918 - CSS Shadow Parts Selector ::part() does not work in combination with :disabled pseudo-class in Chrome

Issue - State: closed - Opened by Dev89787 over 3 years ago - 4 comments
Labels: shadow-dom, question, css

#917 - RfC: API design for aria delegation mechanism

Issue - State: open - Opened by dfreedm over 3 years ago - 14 comments

#917 - RfC: API design for aria delegation mechanism

Issue - State: open - Opened by dfreedm over 3 years ago - 14 comments

#916 - Add delegatesLabel and a content attribute to specify the label element within a shadow tree

Issue - State: open - Opened by rniwa over 3 years ago - 11 comments
Labels: shadow-dom, custom-elements, html-dom, a11y-tracker

#916 - Add delegatesLabel and a content attribute to specify the label element within a shadow tree

Issue - State: open - Opened by rniwa over 3 years ago - 11 comments
Labels: shadow-dom, custom-elements, html-dom, a11y-tracker

#911 - Spring 2021 Virtual Meeting

Issue - State: closed - Opened by JanMiksovsky over 3 years ago - 23 comments

#909 - "open-stylable" Shadow Roots

Issue - State: open - Opened by justinfagnani almost 4 years ago - 281 comments

#909 - "open-stylable" Shadow Roots

Issue - State: open - Opened by justinfagnani almost 4 years ago - 281 comments

#898 - RfC: An alternative approach to accessibility across shadow boundaries

Issue - State: open - Opened by rniwa almost 4 years ago - 3 comments

#898 - RfC: An alternative approach to accessibility across shadow boundaries

Issue - State: open - Opened by rniwa almost 4 years ago - 3 comments

#896 - The MountObserver api, an alternative lazy custom element definition proposal

Issue - State: open - Opened by bahrus almost 4 years ago - 6 comments

#891 - Allow a click on label associated with custom element to focus the custom element

Issue - State: open - Opened by JanMiksovsky about 4 years ago - 5 comments

#887 - declarative-custom-elements: fix error with script export

Pull Request - State: closed - Opened by trusktr about 4 years ago

#887 - declarative-custom-elements: fix error with script export

Pull Request - State: closed - Opened by trusktr about 4 years ago

#877 - Web Components-related breakouts @ TPAC 2020

Issue - State: closed - Opened by hober over 4 years ago - 43 comments

#877 - Web Components-related breakouts @ TPAC 2020

Issue - State: closed - Opened by hober over 4 years ago - 43 comments

#869 - odd custom element placement

Issue - State: closed - Opened by jutunen over 4 years ago - 1 comment

#869 - odd custom element placement

Issue - State: closed - Opened by jutunen over 4 years ago - 1 comment

#864 - Theming options for shadow roots

Issue - State: open - Opened by justinfagnani over 4 years ago - 53 comments

#864 - Theming options for shadow roots

Issue - State: open - Opened by justinfagnani over 4 years ago - 53 comments

#863 - [idea] HTML Modules: Allow exporting without a script

Issue - State: open - Opened by travisleithead over 4 years ago - 7 comments
Labels: modules

#863 - [idea] HTML Modules: Allow exporting without a script

Issue - State: open - Opened by travisleithead over 4 years ago - 7 comments
Labels: modules

#851 - CR/LF fix at end of document

Pull Request - State: closed - Opened by davie-robertson almost 5 years ago

#851 - CR/LF fix at end of document

Pull Request - State: closed - Opened by davie-robertson almost 5 years ago

#848 - Measuring performance of shadow DOM

Issue - State: open - Opened by npm1 almost 5 years ago - 9 comments

#818 - Deprecation warning misleading.

Issue - State: closed - Opened by SanderElias over 5 years ago - 3 comments

#818 - Deprecation warning misleading.

Issue - State: closed - Opened by SanderElias over 5 years ago - 3 comments

#809 - Need a callback for when children changed or parser finished parsing children

Issue - State: open - Opened by rniwa over 5 years ago - 133 comments
Labels: custom-elements, html-dom, needs concrete proposal

#809 - Need a callback for when children changed or parser finished parsing children

Issue - State: open - Opened by rniwa over 5 years ago - 133 comments
Labels: custom-elements, html-dom, needs concrete proposal

#776 - Editor support for WebComponents

Issue - State: open - Opened by octref almost 6 years ago - 48 comments
Labels: question

#776 - Editor support for WebComponents

Issue - State: open - Opened by octref almost 6 years ago - 48 comments
Labels: question

#758 - How to define APIs only for custom element authors

Issue - State: closed - Opened by tkent-google about 6 years ago - 98 comments
Labels: custom-elements

#758 - How to define APIs only for custom element authors

Issue - State: closed - Opened by tkent-google about 6 years ago - 98 comments
Labels: custom-elements

#738 - Custom pseudo-classes for host elements via shadow roots (:state)

Issue - State: closed - Opened by trusktr over 6 years ago - 65 comments
Labels: shadow-dom, needs consensus, css

#738 - Custom pseudo-classes for host elements via shadow roots (:state)

Issue - State: closed - Opened by trusktr over 6 years ago - 65 comments
Labels: shadow-dom, needs consensus, css

#723 - Make custom elements w/ shadowRoot { display: contents } by default

Issue - State: closed - Opened by ndugger over 6 years ago - 18 comments
Labels: custom-elements, needs implementer interest

#661 - Upstreaming Shadow DOM and outstanding v1 work

Issue - State: closed - Opened by annevk about 7 years ago - 10 comments
Labels: v1, shadow-dom, needs spec, blocked

#661 - Upstreaming Shadow DOM and outstanding v1 work

Issue - State: closed - Opened by annevk about 7 years ago - 10 comments
Labels: v1, shadow-dom, needs spec, blocked

#658 - Why do we really need hyphens?

Issue - State: closed - Opened by trusktr about 7 years ago - 33 comments
Labels: custom-elements

#658 - Why do we really need hyphens?

Issue - State: closed - Opened by trusktr about 7 years ago - 33 comments
Labels: custom-elements

#652 - Close this repository in the future

Issue - State: closed - Opened by hayatoito about 7 years ago - 10 comments

#652 - Close this repository in the future

Issue - State: closed - Opened by hayatoito about 7 years ago - 10 comments

#634 - Proposal: Allow custom elements to be in any namespace

Issue - State: open - Opened by hfmanson over 7 years ago - 22 comments
Labels: custom-elements, needs implementer interest

#634 - Proposal: Allow custom elements to be in any namespace

Issue - State: open - Opened by hfmanson over 7 years ago - 22 comments
Labels: custom-elements, needs implementer interest

#632 - fix example so that attachShadow does not throw an exception

Pull Request - State: closed - Opened by dylanb over 7 years ago - 2 comments

#624 - Custom 'void' or self-closing elements (HTML parser changes)

Issue - State: closed - Opened by pfrazee over 7 years ago - 62 comments
Labels: custom-elements, needs implementer interest

#609 - Copying global `<style>` textContent into ShadowDOM roots is not ideal.

Issue - State: closed - Opened by trusktr almost 8 years ago - 10 comments

#609 - Copying global `<style>` textContent into ShadowDOM roots is not ideal.

Issue - State: closed - Opened by trusktr almost 8 years ago - 10 comments

#605 - Constructor arguments in custom elements

Issue - State: closed - Opened by olanod almost 8 years ago - 12 comments
Labels: v2, custom-elements

#605 - Constructor arguments in custom elements

Issue - State: closed - Opened by olanod almost 8 years ago - 12 comments
Labels: v2, custom-elements

#566 - registry: Add an API to retrieve the localName given a custom element constructor

Issue - State: closed - Opened by treshugart about 8 years ago - 57 comments
Labels: custom-elements, needs spec

#566 - registry: Add an API to retrieve the localName given a custom element constructor

Issue - State: closed - Opened by treshugart about 8 years ago - 57 comments
Labels: custom-elements, needs spec

#565 - [idea] Make use of `observedAttributes` optional

Issue - State: closed - Opened by trusktr about 8 years ago - 45 comments

#565 - [idea] Make use of `observedAttributes` optional

Issue - State: closed - Opened by trusktr about 8 years ago - 45 comments

#519 - [idea] Allow HTML Element attributes to accept any type of value, not just strings.

Issue - State: closed - Opened by trusktr over 8 years ago - 39 comments
Labels: custom-elements

#509 - The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension.

Issue - State: closed - Opened by trusktr over 8 years ago - 533 comments
Labels: custom-elements

#509 - The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension.

Issue - State: closed - Opened by trusktr over 8 years ago - 533 comments
Labels: custom-elements

GitHub / WICG/webcomponents issues and pull requests