New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 681897 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

When in "Mobile-friendly view", turning off the screen and turning it back on leaves the view

Project Member Reported by mpear...@chromium.org, Jan 17 2017

Issue description

Google Chrome : 55.0.2883.91 (Official Build) (32-bit)
OS: Android 5.0.02; LG-D801 Build LRX22G
JavaScript: V8 5.5.372.32

When I've swiped up the mobile-friendly view and am reading a page, sometimes things happen that make me put my phone down and/or press the power button to turn off the screen.  Someone comes over to talk to me.  I remember something I must do on the computer.  etc.  When press the power button again to wake up my phone, the mobile-friendly view is gone.  I'm back viewing the regular web page.  Ugh.

Related issues that make this behavior worse:
* This would be less bad if at least the regular page that I'm kicked back to is scrolled to the section that I was reading before.  Instead, it's always at the top, losing my place.
* Also, in the regular view, there is no "Make page mobile friendly" infobar at the bottom.  To get back the ability to read the mobile-friendly view, I have to reload the page.  (And reloading the page is a problem if I'm somewhere without a data connection...)

 
Labels: OS-Android

Comment 2 by wychen@chromium.org, Feb 14 2017

Cc: mdjones@chromium.org k...@chromium.org wychen@chromium.org
Status: Available (was: Untriaged)
mdjones@, could you take a look? Thanks!
IIRC this is a side effect of listening to activity state changes which we did for multi-window support. I'll take a look when I have time.

Comment 4 by klo...@chromium.org, Apr 10 2017

Owner: mdjones@chromium.org
Status: Assigned (was: Available)

Comment 5 by wychen@chromium.org, Apr 10 2017

 Issue 691463  has been merged into this issue.
Status: Fixed (was: Assigned)
This seems fixed to me.

Sign in to add a comment