I probably should have filed this some time ago. I've found and have been using the fact that in the vast majority of cases, for pages that don't display an orange ReaderView button/icon in the awesomebar, I can open the menu and tap the ReadingList icon permanently there, and then switch to the list and open the page in ReaderView. In the new scheme of things, this workaround isn't available. If the ReaderView button is not provided in the addressbar, I can't force add to to ReaderingList, as the button in the Menu is now a combined Bookmarks/Readinglist button based on display context. My new workaround is to paste/append |about:reader?url=| into the addressbar (customized addon time?) ...
s/orange ReaderView button/ReaderView button/
This would be an issue with our `isProbablyReaderable` algorithm: https://github.com/mozilla/readability/blob/master/Readability.js#L1721 If you have testcases, you should file issues (and submit pull requests, if you have ideas to fix them) in that repo. The main thing that makes this tricky is that this function is purposefully very simple for performance reasons (it's called on every page load). You're right that you can force reader mode by going to the about:reader URL directly. It would be simple to write an add-on that always displays the reader view icon. You would just need to monkey-patch the `updatePageAction` function here: http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/Reader.js#184
You need to log in before you can comment on or make changes to this bug.