Issues: WICG/webcomponents
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Use Cases: Iterating and Combining Custom Element Registries
#1057
opened May 3, 2024 by
EisenbergEffect
Question: Any possibile way for cross shadowDom exclusive interactive elements
question
#1054
opened Mar 22, 2024 by
woody-li
[exportparts] support exporting via wildcards
exportparts="*, primary-*"
#1051
opened Mar 8, 2024 by
sorvell
Why is the focus visible when a lightDom element in a web component is clicked?
#1046
opened Jan 24, 2024 by
Garcia-Christophe
[scoped-registries] Consider future expansion to allow using a registry without new API
#1043
opened Jan 8, 2024 by
sorvell
Observing slotchange mutation records: a
SlotChangeObserver
API similar to MutationObserver
with childList:true
#1042
opened Dec 22, 2023 by
trusktr
[scoped-registries] Finding a definition for disconnected elements
#1040
opened Dec 8, 2023 by
sorvell
Allowing for more complex slotted styling by rewriting host rules into global CSS rules
#1038
opened Nov 20, 2023 by
sirisian
Modify :is() and :where() to support selecting derived node types
#1037
opened Nov 19, 2023 by
sirisian
Allow customElementRegistry definitions to persist across page loads
#1033
opened Oct 2, 2023 by
andy-blum
Should browsers do bookkeeping on DOM parts after initial parse?
#1030
opened Sep 15, 2023 by
iteriani
Proposal: Custom attributes for all elements, enhancements for more complex use cases
#1029
opened Sep 13, 2023 by
LeaVerou
Previous Next
ProTip!
Mix and match filters to narrow down what you’re looking for.