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

Issue 702399 link

Starred by 5 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Chrome
Pri: 3
Type: Feature



Sign in to add a comment

FR: Hide desktop top chrome UI during touch-scrolling

Project Member Reported by tdander...@chromium.org, Mar 16 2017

Issue description

Similar to the behavior for Chrome on mobile, consider hiding the browser's top chrome (tabstrip, toolbar, omnibox, bookmarks bar, etc) during touch-scrolling of a webpage.

 
Labels: Proj-TabletChrome-Phase2
Owner: tdander...@chromium.org
Paraphrasing spec from https://docs.google.com/document/d/1D27SB2VV8Nv4pTAZmtiR-Yt_nh9LKMdthwyYaKpVkCE

1. Top-Chrome automatically hides when the user touch-scrolls the page.
2. We only track the root frame of the web page. Scrolling embedded frames or other content does nothing.
3. As the page contents move up (because the user is moving their finger up) the top-chrome moves off-screen at a 1:1 ratio. 
4. If the user stops scrolling while top-chrome is partially visible, then top-chrome will animate-scroll either off-screen (iff we've passed the threshold, currently defined as 75% hidden) or back on-screen (if we haven't passed the threshold)
5. The opposite happens if the user scrolls down when top-chrome is hidden (including the transition thresholds for partial scrolling)
6. For the initial release, we only hide chrome on maximized browsers.

Comment 2 by rpop@chromium.org, Jun 1 2017

Please implement behind a flag, since this hasn't hit UI review yet.
Cc: bruthig@chromium.org tdander...@chromium.org est...@chromium.org moh...@chromium.org
Owner: ----
Status: Available (was: Assigned)
Marking as Available if anyone is interested in poaching.
Cc: rjkroege@chromium.org sadrul@chromium.org fsam...@chromium.org mfomitchev@chromium.org

Comment 5 by rpop@chromium.org, Jun 15 2017

Owner: rpop@chromium.org
Status: Assigned (was: Available)
UX has recommended we block this work until they can staff it. Discussion here: https://docs.google.com/a/google.com/document/d/1D27SB2VV8Nv4pTAZmtiR-Yt_nh9LKMdthwyYaKpVkCE/edit?disco=AAAABNZs0j8

Comment 6 by rpop@chromium.org, Oct 3 2017

Cc: groby@chromium.org
Cc: -mfomitchev@chromium.org

Sign in to add a comment