>>> My Info: Win7_64, Nightly 50, 32bit, ID 20160714030208 (2016-07-14) STR_1: 0. Open url [1] in a new tab 1. Click reader button in urlbar, reload the page (for example, I switched to a pending tab) 2. Click Back button in urlbar once 3. Click Back button in urlbar until you get to the 2nd item in tab history (Step 1) STR_2: 1. Open url [2] in a new tab (I'm a user. I might have created a bookmark with this about:reader url) 2. Click Back button in urlbar once 3. Click Back button in urlbar until you get to the 1st item in tab history (Step 1) > [1] https://ssl.gstatic.com/inputtools/js/msgs/8/en.js > [2] about:reader?url=https%3A%2F%2Fssl.gstatic.com%2Finputtools%2Fjs%2Fmsgs%2F8%2Fen.js AR: Step 1 - browser automatically redirects from about:reader url [2] to normal url [1] Step 2 - browser briefly navigates to desired page, but then redirects to url [1] again Step 3 - browser finally obeys and navigates to about:reader url [2]... only to show a blank page ER: More user-friendly... For example, one of 4 possible scenarios below would be good. I have no idea what are the limitations, but I'd like to see (X) or (T). X) Step 1 - browser shouldn't redirect to other pages. It should open reader mode Y) Step 1 - browser should open reader mode with a description that some unexpected error happened Z) Step 2 - browser should go back to reader mode page, saying that some unexpected error happened T) STR_1 step 0 - browser shouldn't even display reader mode button if it has such troubles Note: STR_1 and STR_2 are describing .js file I tested. It's NOT likely that some articles are stored in .js files. But similar thing happens with text/plain files.

This behaves better now and no longer auto-redirects. Reader mode also works when the button is present in the URL bar, but doesn't seem to work otherwise. I don't think there's anything that needs addressing here.