Open Bug 1166687 Opened 9 years ago Updated 2 years ago

Reader Mode produces different results on NY Times blog article based on real DOM vs. loading page via XHR (likely because of script-based changes to 'real' page if loaded first?)

Categories

(Toolkit :: Reader Mode, defect, P5)

38 Branch
defect

Tracking

()

Tracking Status
firefox38.0.5 --- wontfix

People

(Reporter: cbadau, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [reader-mode-readability-algorithm])

Attachments

(2 files)

Attached image before-page-reload.png
Reproducible on Firefox 38.0.5 Beta 3(BuildID: 20150518141916)
Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0

Steps to reproduce: 
1. Launch Firefox. 
2. Go to http://bits.blogs.nytimes.com//2015/03/30/the-path-toward-tomorrows-internet/. 
3. Click the "Enter Reader View" button from the Location Bar.
4. While the page is in Reader View mode, reload the page. 

Actual results: There are several pieces of text displayed after reloading the page, which were missing before. See attached screenshots. 

Expected results: The page is correctly displayed in Reader View mode (after reload). There should not be any missing text.
None of the extra text is crucial, so P5.
Priority: -- → P5
Summary: Reloading a page while Reader View is active makes additional pieces of text to be displayed → Reader Mode produces different results on NY Times blog article based on real DOM vs. loading page via XHR (likely because of script-based changes to 'real' page if loaded first?)
Whiteboard: [reader-mode-readability-algorithm]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: