- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Mar 2018 21:01:58 +0000
- To: public-css-archive@w3.org
> In particular (maybe I misread how it works), doesn't all the part-forwarding stuff mean that a ::part(..) selector matches differently depending on which scope the selector is declared? No, there's nothing scope-specific about it at all. Could you point to what gave you that impression, so I can fix it in the spec? The parts that an element exposes are just a part of the element's API, like its class list or its ID. Each shadow host just has a parts map, which maps part names to a list of elements (either from its own shadow tree, or a descendant tree if they're forwarding). > Anyway, personally I think Mozilla should take a similar position to Apple here, of supporting the general idea but not any specifics, but I opened mozilla/standards-positions#59 to get a proper official position here. Directing this towards both Moz and Apple: this isn't a useful position to take. :/ We're currently proceeding in implementation on the assumption of support, based on previous statements from both of y'all's companies. "Like the idea, don't know about any details" means you don't like the spec and don't want us to implement, right? Because if we *do* implement, things'll gradually freeze, so you better make sure all the details you're unsure about are indeed something you'd like to see. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2368#issuecomment-369729529 using your GitHub account
Received on Thursday, 1 March 2018 21:02:01 UTC