Container Definitions, manifest, and querySelectors
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 72
- Forks
- 10
- Avg merge
- 9d 15h
- Merged PRs (30d)
- 3
Description
Regarding the conversations on declarative container rules, one idea that came up in discussion is that this is basically equivalent to a style resolution and would work the same way as normal style rules (performance wise). This got me thinking... should it just be a css property?
Strawman:
body > div.mySelector {
container-timing: 'id'; /* or just element-timing */
}
All this would do is provide a hint to the browser that it is worth buffering the timing data for elements, which would still need to be collected by the Observer.
Contributor guide
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 with the linked “Option 2: Declarative Container Rules” section in docs/container-definitions.md, then compare the proposed container-timing CSS property with normal style-rule resolution. The issue names no implementation files or tests; done would require a decided direction and a sufficiently specified proposal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100