Clarify how `<script type=webbundle>` affects speculative HTML parsing.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
We should clarify how <script type=webbundle> affects speculative HTML parsing.
A browser must not fetch a resource from the network speculatively if <script type=webbundle> says the resource should be fetched from the bundle.
Regarding a browser's implementation, the chromium already implements this kind of behaviour in html_preload_scanner, as far as I understand correctly.
Note that this was pointed out here. Much appreciated!
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 speculative HTML parsing section linked in the issue and compare its wording with Chromium's html_preload_scanner.cc implementation. Done means the specification clearly states that a resource identified by <script type=webbundle> must not be fetched speculatively from the network when it should come from the bundle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100