MicrosoftEdge / MicrosoftEdge/MSEdgeExplainers
[@sheet] Shadow DOM stylesheet inheritance
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.4k
- Forks
- 286
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 8
Description
Given a hierarchy of global root G > a shadow root A > shadow root B, if a stylesheet with @sheet foo is added to G and a different @sheet foo added to A, how should they compose as adopted by B?
Related: #900, #933, #935, #937, #938 (about half of the existing @sheet-related issues)
This issue leads me more in favor of an HTML-based solution, FWIW.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read related issues #900, #933, #935, #937, and #938 first; no file, test, or implementation entry point is specified. The work is done when the composition semantics for @sheet across global root G, shadow root A, and shadow root B are defined, including how the two foo stylesheets adopted by B compose.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100