Links to manifest members should be in <code>
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- html, markdown
- Domain
- documentation
Research direction
Start with files/en-us/web/progressive_web_apps/manifest/index.md, then trace the macro that generates the links under “Members.” Check the rendered page to confirm the member names appear in <code> elements; the issue is done when those links use monospaced text.
Written by the indexing model from the issue text.
Description
MDN URL
https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Manifest
https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Manifest/Reference
What specific section or headline is this issue about?
Members
What information was incorrect, unhelpful, or incomplete?
The links under the members headline is generated using a macro. All these links are the names of members and should be written in <code>
What did you expect to see?
monospaced words
Do you have any supporting links, references, or citations?
No response
Do you have anything more you want to share?
No response
MDN metadata
Page report details
- Folder:
en-us/web/progressive_web_apps/manifest - MDN URL: https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Manifest
- GitHub URL: https://github.com/mdn/content/blob/main/files/en-us/web/progressive_web_apps/manifest/index.md
- Last commit: https://github.com/mdn/content/commit/5f2a755c4fa7d126f85b56fbca90b15c5f039eff
- Document last modified: 2025-08-08T16:55:34.000Z
- Dominant language
- Markdown
- Stars
- 11.1k
- Forks
- 23.3k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 214
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from mdn/content
-
ruby-position: Add a Bopomofo (`inter-character`) examplePossibly taken @Devehab claimed this 5 days ago. OpenContent:CSS help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Content:WebExt needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
NavigateEvent.sourceElement should mention null for cross-origin initiatorsMay be free again @Stackforge-07 claimed this 10 days ago, and no pull request is open. OpenContent:WebAPI needs BCD update
Difficulty 1/5 Under an hour Newbie friendliness 76/100
mdn/content#46189 · 2 comments ·
Maintainers usually reply within 1 day
-
Add a page for flow-tolerancePossibly taken @BaconMan1168 claimed this 27 days ago. OpenContent:CSS document not written needs BCD update
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
WebAuthn Attestation purpose and neccessity is incorrectMay be free again A pull request for this issue was closed without being merged. Openarea: WebAuthn Content:WebAPI
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
mdn/content#45753 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
Similar issues
-
content-freshness: staleOwnedContent doc comments still say 'complete receipt' (follow-up to #7912)Opentriage:bug-verified
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Guide to API useageOpen
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
chipsalliance/verible#2644 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100