MicrosoftEdge / MicrosoftEdge/MSEdgeExplainers
[Declarative Shadow DOM Style Sharing] Suggestions for improving problem statement
Open
Nobody has claimed this yet.
DeclarativeShadowDOMStyleSharing
- Dominant language
- HTML
- Stars
- 1.4k
- Forks
- 286
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 8
Description
The main issues with using <style> in declarative Shadow DOM (DSD) are:
- It's not equivalent to adopting a stylesheet since the sheet is not shared between different shadowRoots. A shared sheet can be modified and any shadowRoots in which it's adopted are automatically updated. There is currently no way to do this with DSD
- Identical styling must be re-emitted as HTML as many times as it's used. This bloats the HTML size of the document. Some of the cost can be easily mitigated via compression and also since browsers likely optimize actual creation of stylesheets. However, the strings must be decompressed and parsed and this adds needless extra work.
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
No files, tests, or entry points are named. Start by reading the two listed limitations and the surrounding Declarative Shadow DOM explainer; identify the intended problem-statement changes and confirm the scope with maintainers before editing. Done means an agreed, clearer statement that accurately covers stylesheet sharing and repeated HTML styling costs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation, web-dev
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100