Avoid overloading web standard slots?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 46
- Avg merge
- 10m
- Merged PRs (30d)
- 2
Description
Now that declarative shadow DOM is available cross browser, it might be a good idea to respect <slot>/slot= inside WebC templates.
Web's own slots could be renamed to something like <webc:slot>/webc:slot=.
Similarly, WebC could avoid doing special handling of <template> by default. I've encountered very strange issues when creating WebC wrappers over <template shadowrootmode="open">.
See also: #185
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
Start by reviewing WebC's handling of , slot=, and , then read the related issue #185. Clarify whether native declarative shadow DOM slots and templates should be preserved by default and which WebC-specific names should replace current handling; done requires an agreed design and tests covering these cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100