WICG / WICG/declarative-partial-updates
Paint holding
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 135
- Forks
- 13
- Avg merge
- 12m
- Merged PRs (30d)
- 3
Description
As discussed in the WebPerfWG call, I'm just noting down the thoughts for public discussion.
I asked how the spec would treat painting / paint holding (e.g. during a navigation).
@noamr mentioned that is out of the scope for now (as this is more a primitive, so not related to navigations). So it would e.g. need a user land JS implementation that holds the paint (via CSS display:none or something), or using View Transitions for individual elements/nodes.
An idea I had was using the <link rel="expect" blocking="render" href="#id"> tag — which if inserted could hold paint until #id is also patched in.
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
No file, test, or implementation entry point is identified. Start by reviewing the referenced WebPerfWG discussion and determining whether paint holding belongs in this specification; the issue does not define acceptance criteria or what would constitute done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html, javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100