- From: robglidden <notifications@github.com>
- Date: Mon, 18 Mar 2024 16:03:23 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <WICG/webcomponents/issues/1052/2005229757@github.com>
From [shadow layers](https://github.com/WICG/webcomponents/issues/909#issuecomment-1993388146) proposal ([noting](https://github.com/WICG/webcomponents/issues/909#issuecomment-2005039901) they may be a bit over-broad particularly as to coordination scenarios): ## Use Cases Addressed - **Include all document CSS as a low priority layer inside a shadow tree.** This is the heart of a solution to the original issue as opened. - **Support both declarative and imperative use.** Declarative shadow trees are fully supported from the onset, as well as imperative use cases. - **Include selected document CSS as a layer inside a shadow tree.** Selected named outer layers can be brought into a shadow tree by either a shadow tree designer or shadow tree user. - **Enable layer reprioritization.** Inner and outer context layers can be intermixed and reprioritized. - **Enable shadow tree designers to bring in document CSS without intervention by a shadow tree user.** If desired, a shadow tree designer can bring in all of or just selected layers of the document outer context CSS, without intervention of the shadow tree user. - **Enable coordination between shadow tree designers and shadow tree users.** Either can bring in and repriortize outer layers. - **Enable shadow tree user to add and repriortize layers originally provided by shadow tree designer.** A user can bring in any chosen outer layer, not just those pre-defined by a designer. - **Enable a shadow tree designer to "advertise" to shadow tree users the CSS priorities of a shadow tree's inner context.** A designer can expose, publish, or document the original layer order of a shadow tree, so that a user can knowingly adjust it or add to it. - **Polyfillable.** As hopefully implied by this proof of concept implementations. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/1052#issuecomment-2005229757 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/1052/2005229757@github.com>
Received on Monday, 18 March 2024 23:03:28 UTC