WICG / WICG/declarative-partial-updates
Associated Client Hint (or equivalent)
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 135
- Forks
- 13
- Avg merge
- 12m
- Merged PRs (30d)
- 3
Description
In an environment that doesn't support partial updates where JS fails to load or is unsupported (where a polyfill would fail to load), HTML output that includes partial update directives and associated <template> tags will most likely be unusable, displaying perpetual pending states.
It would be helpful if there were some way for a user agent to signal to the server that it supports this feature, so that application servers could intelligently adapt rendering methods and elegantly fall back to a "full" render. Client Hints seem like a natural fit.
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 repository files or tests are named. Start by reviewing the partial update directives, associated template tags, and the Client Hints concept described in the issue; done requires a settled proposal for signaling support and defining the full-render fallback behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- backend, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100