I did a first-pass QA check of a compiled list of popular, Tech and design websites. The most common issues revolve around scraping the "hero" or "lead" image. Moreover, there are sites from this list that are not appearing as Reader View compatible. Etherpad with feedback: https://firefox-ux.etherpad.mozilla.org/reader-comparisons

Here's the list of sites, however this list is too big. (High Traffic for existing Firefox users) https://www.yahoo.com/ http://www.youtube.com/ http://www.wikipedia.org http://www.blogspot.com (* subdomain sites) http://www.about.com http://www.craigslist.org http://www.huffingtonpost.com http://www.answers.com http://www.ehow.com http://www.wordpress.com (* subdomain sites) (High Traffic in general) http://www.nytimes.com/ http://www.washingtonpost.com/ http://www.cnn.com/ http://www.huffingtonpost.com/ http://www.buzzfeed.com/ http://www.usatoday.com/ http://www.wikipedia.org/ http://espn.go.com/ http://www.imdb.com/ http://www.msn.com/ http://www.aol.com/ http://www.foxnews.com/ http://www.forbes.com/ http://www.dailymail.co.uk http://www.businessinsider.com/ http://www.wsj.com/ http://www.bbc.com http://www.tmz.com/ http://www.webmd.com/ http://www.ign.com/ http://lifehacker.com/ http://www.npr.org/ http://mashable.com/ (Tech + Design) http://www.theverge.com/ http://alistapart.com/ http://thenextweb.com/ http://techcrunch.com/ http://www.fastcompany.com/ http://arstechnica.com/ https://medium.com/ https://www.tumblr.com/ http://www.pcmag.com/ http://www.cnet.com/ http://www.venturebeat.com http://qz.com/ http://engadget.com

A quick update here: in-depth Readability.js testing has been started for a while now, with the current progress available in the following etherpad - https://etherpad.mozilla.org/Fx38-Readability. As of this moment, issues have been filed with the Readability GitHub Repository and will be tracked there in the future as well, for each of the websites available in the list from Comment 1.

Let's call this WFM as a lot of issues have been addressed since this got filed, and with the actual issues being kept in github, it's not clear that keeping this open has value.

How is this marked as resolved? Is it because it because on newer version of Firefox above 43.0.1 it shows page sections content properly? If so, it would be nice to not have to update Firefox software and just, maybe, a plugin. I am seeing missing page content exists. When going to http://www.whw1.com, I believe only 1 or 2 sections of content are shown (as combined), and rest are not displayed. I tried it on my own Tech Notes site and it does a relatively fine job. It seems to understand blog style sites better than normal websites. I checked with Firefox 43.0.1. Also, maybe ability to push the right mouse button and get a choice to use Reader View in a page selection would be good; as a suggestion, if it is just not possible to have it recognize all sections of a website page and this way a person can selectively choose.

(In reply to Tech Notes from comment #4) > How is this marked as resolved? Because the issues that Michael filed are largely fixed or have their own independent bugs. It's no use keeping the bug open when it has 1001 issues in it because it makes it difficult to track the individual sites. > I am seeing missing page content exists. When going to http://www.whw1.com, > I believe only 1 or 2 sections of content are shown (as combined), and rest > are not displayed. Please file new individual bugs for individual websites that don't work well. Please make sure to check on the most recent version of Firefox (not 43, which is a year old now and has known security issues). > Also, maybe ability to push > the right mouse button and get a choice to use Reader View in a page > selection would be good; as a suggestion, if it is just not possible to have > it recognize all sections of a website page and this way a person can > selectively choose. Please file a separate bug for this, too.

(In reply to :Gijs Kruitbosch from comment #5) I am only aware of the 2 report #s listed here https://wiki.mozilla.org/QA/Reader_view. Are there other Bug Report numbers associated? List somewhere? and if yes, where? Again, IMO, for the future (if not already in works), this should be separated from Firefox in a way that it does not require an update of FF software and something like a plugin/extension update takes care of it instead.

(In reply to Tech Notes from comment #6) > (In reply to :Gijs Kruitbosch from comment #5) > I am only aware of the 2 report #s listed here > https://wiki.mozilla.org/QA/Reader_view. Are there other Bug Report > numbers associated? List somewhere? and if yes, where? These are all the open reader mode bugs: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=prod%3DToolkit%20comp%3Areader&list_id=13354074 There are some more filed on github: https://github.com/mozilla/readability/issues > Again, IMO, for the future (if not already in works), this should be > separated from Firefox in a way that it does not require an update of FF > software and something like a plugin/extension update takes care of it > instead. If we did this it would likely be a system add-on. Either way, you'd still have to update from 43... I filed bug 1324222 for this.