Madhava Enros [:madhava] Reporter
	Description • 13 years ago

We should design and implement a reading mode in the mobile browser.

At the basic end, this could just be a way to pull content out of bad-for-reading pages into something more purpose-built for reading. At the more sophisticated end of the spectrum, it could be a replacement for dealing with a site's own nav system.

	Patryk Adamczyk [:patryk] UX
	Comment 1 • 13 years ago

Design Concepts can be found here:
https://wiki.mozilla.org/Fennec/NativeUI/UserExperience/ReaderMode

	Mark Finkle (:mfinkle) (use needinfo?)
	Comment 2 • 12 years ago

(In reply to Patryk Adamczyk (UX) from comment #1)
> Design Concepts can be found here:
> https://wiki.mozilla.org/Fennec/NativeUI/UserExperience/ReaderMode

This is a great overview of the feature. I think a hard problem we'll need to figure out to get this working well is:

* What rules do we use to "modify" a webpage to make it work in reading mode?

Each page will have content and images in a different layout. Trying to figure out what is content and what is cruft will be a challenge. Trying to figure out what images are relevant to the text content and which are ads (or other) will be hard too.

We could make some "add-ons" for specific websites, but that won't scale very well. We could have some fallback rules that work in general, but might not work very well.

	Patryk Adamczyk [:patryk] UX
	Comment 3 • 12 years ago

Here is a link (http://www.readability.com/publishers/guidelines/) on readability.com to article publishing guidelines which could be a good start on setting rules for what gets converted into a more readable format. Its using the hNews spec.

	Matt Brubeck (:mbrubeck)
	Comment 4 • 12 years ago

To extract the text content from web sites, my "Reading List" add-on for XUL Fennec uses code from the original Readability bookmarklet, which was released under the Apache 2.0 license.

	Lucas Rocha (:lucasr)
	Comment 5 • 12 years ago

Turning this bug into a meta bug.

	Paul [pwd]
	Comment 6 • 12 years ago

It took me far too long to work out how to use this feature. Is there any chance we can get a popup or open a page that explains these pages are added to the bookmarks?

	Ian Barlow (:ibarlow)
	Comment 7 • 12 years ago

Paul, what were the pain points for you?
Thanks
Ian

	Paul [pwd]
	Comment 8 • 12 years ago

Just figuring out how to find the reader and read things via it. It's not a very intuitive experience for me. The last place I looked was where I found it (bookmarks). I would've been nice if something said "Items added to your reading list can be found in a more reading friendly format via your bookmarks". Also you should be able to remove and/or save reading position of things via the about:reader UI.

	Ian Barlow (:ibarlow)
	Comment 9 • 12 years ago

Yep, these are all things in the pipeline that are coming soon

* Exposing the reading list more clearly to the user
* Next / Prev controls for Navigating through articles in the reading list 
* Removing items from the list

Stay tuned :)

	Paul [pwd]
	Comment 10 • 12 years ago

Is there anyway to hide the icon in the URL bar?

	Kevin Ernst
	Comment 11 • 12 years ago

Perhaps a comment here about "hey, look what they (iOS developers) are doing over there" would not be appreciated here. But responses from Fennec developers on the recent Reddit IAmA (http://www.reddit.com/r/IAmA/comments/vkwjz/iama_significant_portion_of_the_firefox_for/) have emboldened me to make this recommendation:

I cannot emphasize enough how sublime Tweetbot's "reader mode" and offline reading features are, although it capitalizes on integration with third-party services like Instapaper (a Fennec feature request in itself). No other iOS app I know of, with the possible exception of Reeder by Silvio Rizzi, even comes close. Tweetbot's mobile/offline reading workflow is very, very worthy of emulating in Fennec.

If you've never used Tweetbot (or Reader), please consider borrowing a friend's iPhone and having a look at the long-press functionality (see also bug #769374) and the mobilizer "switch" in the toolbar of the baked-in browser.

	Aaron Train [:aaronmt]
	Comment 12 • 11 years ago

This doesn't still need sec-review now does it? I think this bug can be resolved.

	Mark Goodwin [:mgoodwin]
	Comment 13 • 11 years ago

(In reply to Aaron Train [:aaronmt] from comment #12)
> This doesn't still need sec-review now does it? I think this bug can be
> resolved.

No, this has been done: see bug 785077.

	Kevin Brosnan [Ex-Mozilla]
	Comment 14 • 11 years ago

This bug was done for Firefox 14.