Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Declarative Shadow DOM #12

Closed
bennypowers opened this issue Jun 29, 2022 · 5 comments
Closed

Declarative Shadow DOM #12

bennypowers opened this issue Jun 29, 2022 · 5 comments
Labels
concerns: integration Can't be used w/ other web platform features (or unclear what happens if used together) from: Google Proposed, edited, or co-edited by Google. position: support topic: dom Spec relates to DOM (Document Object Model) topic: web components venue: WHATWG DOM Workstream

Comments

@bennypowers
Copy link

bennypowers commented Jun 29, 2022 •
edited by annevk
Loading

Request for position on an emerging web specification

  • WebKittens who can provide input: @rniwa

Information about the spec

Design reviews and vendor positions

Bugs tracking this feature

Anything else we need to know

Would unblock shadow DOM use in above-the-fold content in performance sensitive pages and applications.
@rniwa
Copy link
Member

rniwa commented Jun 29, 2022

One open issue I have with this feature is the compatibility with scoped custom element registry. I'd like to figure out how these two features fit together before shipping either.

@othermaciej othermaciej added topic: dom Spec relates to DOM (Document Object Model) topic: web components labels Jun 29, 2022
@leobalter leobalter mentioned this issue Jun 29, 2022
Closed
@marcoscaceres marcoscaceres changed the title RFP: Declarative Shadow DOM Declarative Shadow DOM Jun 30, 2022
@hober hober added the concerns: integration Can't be used w/ other web platform features (or unclear what happens if used together) label Jun 30, 2022
@thescientist13
Copy link

thescientist13 commented Jul 17, 2022 •
edited
Loading

@rniwa
Opened up an issue for tracking Scoped Custom Element Registries

@othermaciej othermaciej added the from: Google Proposed, edited, or co-edited by Google. label Sep 25, 2022
@rniwa
Copy link
Member

rniwa commented Sep 27, 2022

We're prototyping this in https://bugs.webkit.org/show_bug.cgi?id=245556

@annevk
Copy link
Contributor

annevk commented Oct 11, 2022

Given that we're actively prototyping and helping out with standardization I would suggest we add the "position: support" label one week from today.

@hober
Copy link
Member

hober commented Mar 23, 2023

Closing as we've identified our position.

@hober hober closed this as completed Mar 23, 2023
@hober hober moved this from Unscreened to Done in Standards Positions Review Backlog Mar 23, 2023
@mfreed7 mfreed7 mentioned this issue Sep 15, 2023
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
concerns: integration Can't be used w/ other web platform features (or unclear what happens if used together) from: Google Proposed, edited, or co-edited by Google. position: support topic: dom Spec relates to DOM (Document Object Model) topic: web components venue: WHATWG DOM Workstream
Projects
Standards Positions Review Backlog
Status: Done
Milestone
No milestone
Development

No branches or pull requests
6 participants
@hober @rniwa @thescientist13 @othermaciej @bennypowers @annevk