-
Notifications
You must be signed in to change notification settings - Fork 378
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
[declarative-custom-elements] do we need DOM parts or any template mechanism in spec?
#1090
opened Dec 6, 2024 by
mildred
Reference Target: How should we treat invalid reference targets for relations set via Element IDL attributes?
#1089
opened Dec 5, 2024 by
alice
case-sensitive access to HTML attributes (as they were written) would be useful for framework authors
#1076
opened Oct 13, 2024 by
trusktr
Form associated custom elements: cross shadow root form participation
#1075
opened Oct 6, 2024 by
christophe-g
Web components authors are currently using ARIA in problematic ways that lead to duplicate announcements
#1073
opened Sep 25, 2024 by
aleventhal
Reference Target: Should the
form
and list
JavaScript attributes return the host element?
#1072
opened Aug 22, 2024 by
behowell
event.composedPath()[0] can be very slow: add event.composedTarget?
#1070
opened Aug 20, 2024 by
justinfagnani
Use Cases: Iterating and Combining Custom Element Registries
custom-elements
#1057
opened May 3, 2024 by
EisenbergEffect
Possibile way for cross shadowDom exclusive interactive elements
question
#1054
opened Mar 22, 2024 by
woody-li
Previous Next
ProTip!
Updated in the last three days: updated:>2024-12-19.