1. add items to RL 2. click on a article in the RL sidebar actual: always displays in Reader View mode. expected: it should display in the mode that it was added or match the desktop experience(displays in the mode that you're currently in)
AFAIK, it should open in the mode you added it in. Since we do not have a "side bar" as per desktop. We do not have this "mode" that you stay in. CC'ing margaret. Didn't we used to open the link in Reader View or not based on how you added to RL (in Reader View vs. not)?
(In reply to Anthony Lam (:antlam) from comment #1) > AFAIK, it should open in the mode you added it in. Since we do not have a > "side bar" as per desktop. We do not have this "mode" that you stay in. > > CC'ing margaret. Didn't we used to open the link in Reader View or not based > on how you added to RL (in Reader View vs. not)? No, we have always attempted to open the page in reader view, and we just fall back to the original URL if that fails. I understand this behavior is inconsistent with desktop, but there isn't a straightforward way to do this with our current implementation, so I think changing this behavior is out of the scope of what we can do for Fx38.
In that case, would it make sense to change Desktop to match Mobile? (I'll be honest, I expected Desktop to behave like Mobile, and was surprised when it didn't.)
I might be less opinionated about this - but the fact that toggling Reader View back to normal view causes a refresh - creates a user cost. Desktop has the correct behavior: opens the URL in the current mode you're in (i.e. currently in RV clicking displays in RV, currently in normal clicking displays in normal) As for mobile - this seems like central to the experience, opening a item from RL, and will put undue pressure on RV rendering properly. It would be much better to default the other way around... Normal mode as default and you must tap the RV book icon to switch it. Can we at least flip that around?
The current Mobile behavior has been in use for over a year. I don't think we're going to change it as a knee-jerk reaction to a choice made on Desktop. Let's get some thoughtful UX on this. No need to push it for Fx38.
Another thing to consider is that for mobile, we currently cache the article content for offline use. If we changed this behavior, we wouldn't automatically have offline support. Also, this is similar to what services like Pocket do - show a readerized version of the content, but default to the original content if we couldn't parse it as an article.
got mixed up with desktop - this isn't a regression, this is current behavior. I'm fine to defer to future release.
Component: Reading List → Awesomescreen
You need to log in before you can comment on or make changes to this bug.