WebAssembly / WebAssembly/spec
[bikeshed] Issues with content blocking on Safari
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 3.5k
- Forks
- 539
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 13
Description
The FPWD at https://www.w3.org/TR/2022/WD-wasm-core-2-20220419/
Seems near empty, with a table of contents pointing at a different document: https://www.w3.org/TR/2022/WD-wasm-core-2-20220419/intro/introduction.html
And those two documents have conflicting sections. e.g. the latter, in section 1.1, says it is the product of a CG.
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 by comparing the FPWD at https://www.w3.org/TR/2022/WD-wasm-core-2-20220419/ with its linked introduction document, https://www.w3.org/TR/2022/WD-wasm-core-2-20220419/intro/introduction.html. Trace the Bikeshed publication entry point that produces the table of contents and sections. Done means the published FPWD has consistent content and section metadata rather than pointing to a conflicting document.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100