New York Times glossary spans should be removed from reader mode
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- web-dev
Research direction
No source file or test is named. Start with the New York Times HTML example and the linked Bugzilla report, then identify where reader mode processes the glossary-wrapper markup; done means glossary-info content is absent from the resulting reader view while the glossary-text remains.
Written by the indexing model from the issue text.
Description
From https://bugzilla.mozilla.org/show_bug.cgi?id=1544594
Some NYT articles include markup like this:
<span class="glossary-wrapper">
<span class="glossary-text">transparency</span>
<span class="glossary-info">
<span class="glossary-definition">Taking appropriate measures to provide any information relating to processing to the data subject in a concise, intelligible and easily accessible form, using clear and plain language. <a href="https://www.nytimes.com/interactive/2019/04/10/opinion/internet-privacy-terms.html" target="_blank">Glossary</a>
</span><img class="close-tooltip" src="https://static01.nyt.com/newsgraphics/2019/01/22/tooltip-template/1e41ab3eab12f1354e056fb2fa3acc6d09df13e2/close.svg" alt="Close X">
</span><span></span></span>
We should be removing the glossary-info bits.
- Dominant language
- JavaScript
- Stars
- 11.5k
- Forks
- 732
- PR merge metrics
- No merged PRs in 30d
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.
More from mozilla/readability
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
mozilla/readability#1026 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mozilla/readability#997 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
mozilla/readability#1031 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
mozilla/readability#1029 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
mozilla/readability#1024 ·
All issues in mozilla/readability
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100