Context
glossary.html ships with <li class="wall-empty">Loading the glossary…</li> in the markup and a count reading "Loading…". With JavaScript off, both stay there permanently and the page looks broken rather than degraded.
What to change
Files: glossary.html
Requirements:
- Use a
<noscript> block to tell the reader what happened and what to do
- The message must explain that the glossary needs JavaScript, not just say "error"
- Point them at
data/glossary.json, which is readable directly
- Leave the normal loading state alone for people who do have JavaScript
Acceptance criteria
How to verify locally
Open the page, then disable JavaScript in dev tools (Command Palette → "Disable JavaScript") and reload.
python3 -m http.server 8000
Then open http://localhost:8000.
Difficulty
Beginner. The contributor wall has the same gap if you want to fix both.
New here? Comment /claim on this issue and a bot will assign it to you. Then read CONTRIBUTING.md.
Stuck at any point? Comment here saying what you have tried and where it stopped working — that is not an admission of failure, it is how we find out the instructions were unclear. You can also come to a PR Debug Clinic (Oct 12 or Oct 21).
Context
glossary.htmlships with<li class="wall-empty">Loading the glossary…</li>in the markup and a count reading "Loading…". With JavaScript off, both stay there permanently and the page looks broken rather than degraded.What to change
Files:
glossary.htmlRequirements:
<noscript>block to tell the reader what happened and what to dodata/glossary.json, which is readable directlyAcceptance criteria
How to verify locally
Open the page, then disable JavaScript in dev tools (Command Palette → "Disable JavaScript") and reload.
Then open http://localhost:8000.
Difficulty
Beginner. The contributor wall has the same gap if you want to fix both.
New here? Comment
/claimon this issue and a bot will assign it to you. Then read CONTRIBUTING.md.Stuck at any point? Comment here saying what you have tried and where it stopped working — that is not an admission of failure, it is how we find out the instructions were unclear. You can also come to a PR Debug Clinic (Oct 12 or Oct 21).