"Autohide shelf" option is inconsistent when swiping and full-screening
Reported by
realgran...@gmail.com,
May 26 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9334.72.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.140 Safari/537.36 Platform: 9334.72.0 (Official Build) stable-channel cave Steps to reproduce the problem: 1. Check "autohide shelf" in shelf options 2. Swipe up from edge on touchscreen 3. What is the expected behavior? The shelf reveals but the autohide option remains What went wrong? Autohide option is permanently removed whenever the touchscreen edge swipe is done Did this work before? N/A Chrome version: 58.0.3029.140 Channel: stable OS Version: 9334.72.0 Flash Version: Shockwave Flash 25.0 r0 It has generally inconsistent behavior: for example when app is in fullscreen/immersive mode the swipe up on touchscreen does temporarily reveal the shelf and the autohide option is even not there (it is hidden when you clidk/long-press) but is still unchecked even when it is not displayed and the UX logic here is that in immersive mode it can be revealed only temporarily and is always "autohide" - yet autohide option is unchecked the very first time I temporarily reveal it.
,
Jun 2 2017
,
Jun 9 2017
Do you feel we shouldn't bring back the shelf forever when you swipe from bottom?
,
Jun 9 2017
,
Jun 9 2017
At least it should be consistent. In immersive mode there is no option to autohide because in immersive mode it is always auto-hidden. But still when you swipe bottom up the "autohide" option is deselected (it can be seen later when you exit immersive mode and it is indeed un-checked after you used swipe to temporary reveal panel in immersive mode where autohide is obviously always ON). At maximum, one should propose a state-consistent UX policy how this is handled. To my intuitive vision, swipe should not affect any hidden properties since property (saved state) modification and finger swipe are different domains from the UX perspective. The fact that "autohide" option is accessible via right-click and not via finger tap supports the idea that ideologically these are from different domains and should not affect each other.
,
Aug 22 2017
,
Nov 28 2017
,
Oct 4
Fixed in M71 |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by realgran...@gmail.com
, May 26 2017