Reader mode not offered on WHATWG specs because of 'home page' detection




Reader Mode
2 years ago
2 years ago


(Reporter: Domenic Denicola, Unassigned)


(Blocks: 1 bug)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [reader-mode-readability-algorithm][reader-mode-isreadable-detection], URL)



2 years ago
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160315153207

Steps to reproduce:

Browser to in one tab, and in another

Actual results:

In the first tab, reader mode is not offered. In the second, it is.

This is because of the "home page" check in

Expected results:

Reader mode should have been offered in both.

This effects all other specs listed at (e.g. HTML, DOM, URL, etc.)


2 years ago
Blocks: 1102450
Component: Untriaged → Reader Mode
OS: Unspecified → All
Product: Firefox → Toolkit
Hardware: Unspecified → All

Comment 1

2 years ago
(In reply to Domenic Denicola from comment #0)
> This is because of the "home page" check in
> ReaderMode.jsm#334

Yes, unfortunately getting rid of this would break lots of more commonly used sites for the general web population (that is, we'd offer reader mode on homepages of nytimes and the like when we shouldn't). I don't really have any amazing ideas about how to fix this. There are a number of constraints, including not regressing loading performance (we can't really spend more than 2-3ms evaluating whether a document should offer reader mode when loading it). If you have suggestions, they'd be very welcome! In the meantime, going to downprio this because we should fix even grosser offences first (like dropping entire paragraphs/sections out of CNN articles etc.).
Ever confirmed: true
Priority: -- → P5
Summary: Reader mode not offered on WHATWG specs → Reader mode not offered on WHATWG specs because of 'home page' detection
Version: 45 Branch → Trunk


2 years ago
Whiteboard: [reader-mode-readability-algorithm][reader-mode-isreadable-detection]

Comment 2

2 years ago
Maybe you could consider searching for a specific meta tag, e.g. <meta name="offer-reader-mode" content="true">? (I guess content="false" could be used as an opt-out for incorrect detections... although maybe that would just be abused by pages that don't want reader mode hiding their ads.)
You need to log in before you can comment on or make changes to this bug.