Some of the lazy loaded images in "The Conversation" are not shown unless the whole article has been scrolled before entering reader view
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
Research direction
No repository file or test is identified in the issue. Reproduce the behavior with the listed The Conversation articles in Firefox Reader view and Epiphany's WebKitGTK reader view, then compare which lazy-loaded content images are present before and after scrolling; done means all article images appear without prior scrolling.
Written by the indexing model from the issue text.
Description
Many articles in this scientific news site exhibit this behavior: in-content lazy-loaded images within the articles, below the hero header image (a.k.a. below the "fold"), some content images do not show up in Reader view, unless you scrolled through the page's contents to force loading them before entering reader view.
Here are some example articles, as the behavior varies quite a bit from one article to the next:
- Article 221954 (on unaffordable housing) : there are two photos inside the contents of the article, none of them show up in reader view until you have scrolled through them
- Article 224832 (on natural ecosystems) also has two photos in the article's contents; the first photo (strawberries) shows up in Reader view even if you enter the view without scrolling first, but the second photo (bumblebee and purple/blue flowers) only shows up in Reader view if you had scrolled to it first.
- Article 208352 (on business school education) load all their images in Reader mode even without scrolling.
- Article 209832 (on AirBnB and gentrification) loads its first two images, but not the third one
I have tested these on Firefox 123's built-in Reader view, and in Epiphany 45's (WebKitGTK) reader view; both behave the same.
- 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