Output doesn't match Firefox Reader View
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.5k
- Forks
- 732
- PR merge metrics
- No merged PRs in 30d
Description
I've tried this on a number of sites simply by copying the readability.js script into the console and then executing it on the page and the output doesn't seem to match the Firefox reader view at all. Headers and Nav are still left on the page and the page just seems a bit broken/off compared to the readerview. Is the logic used by Firefox different/augmented?
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 reproducing the reported behavior with the readability.js script copied into a browser console and compare its output with Firefox Reader View. Focus on the remaining headers and navigation and the broken layout; the issue is complete when the discrepancy is reproduced and its cause or a concrete regression test is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100