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

Issue 646977 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Blocking:
issue 558575



Sign in to add a comment

[scroll anchoring] interactions with extension settings page "developer mode" checkbox

Project Member Reported by skobes@chromium.org, Sep 14 2016

Issue description

What steps will reproduce the problem?
1. Enable scroll anchoring
1. Go to chrome://extensions/ with some extensions installed (e.g. corp account)
2. Scroll down or to the right a tiny bit (so you are not at 0,0)
3. Click the "developer mode" checkbox

What is the expected result?
A row of buttons appears below the header.

What happens instead of that?
Scroll anchoring anchors to the first item in the extension list, which is pushed down by the buttons.  (The header is skipped due to being position:fixed.)  The scroll anchoring adjustment causes the buttons to be offscreen.

(This breaks AutoScrollExtensionSettingsWebUITest.testAutoScroll in  issue 597479 .)
 

Comment 1 by ymalik@chromium.org, Sep 14 2016

I think that's the right thing to do no? For example, without scroll anchoring, pressing that button while you're scrolled down a bit causes a jump (and doesn't really bring the buttons into view anyway). 

I do notice a judder when toggling the button though (tested a mac). 

Comment 2 by skobes@chromium.org, Sep 14 2016

I agree it's the right thing if you've scrolled down by more than the height of the buttons.

It's less obviously right if you're only scrolled to the right, or if you've scrolled down by just a few pixels.

Comment 3 by ymalik@chromium.org, Sep 14 2016

Right. I think we shouldn't make adjustments in the direction of the zero scroll position.

The latter sounds like the fundamental problem of anchoring where the change happens within the viewport but above the anchor element.
Project Member

Comment 4 by bugdroid1@chromium.org, Sep 14 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/101eea619734b9b9362b5557f2999317ea743a0b

commit 101eea619734b9b9362b5557f2999317ea743a0b
Author: skobes <skobes@chromium.org>
Date: Wed Sep 14 21:29:41 2016

Workaround for scroll anchoring issue with AutoScrollExtensionSettingsWebUITest.

BUG= 646977 

Review-Url: https://codereview.chromium.org/2343683002
Cr-Commit-Position: refs/heads/master@{#418680}

[modify] https://crrev.com/101eea619734b9b9362b5557f2999317ea743a0b/chrome/browser/ui/webui/extensions/extension_settings_browsertest.js

Comment 5 by skobes@chromium.org, Sep 14 2016

Blocking: -597479 558575

Comment 6 by ojan@chromium.org, Sep 15 2016

Hm...that's interesting. I agree with Yash that the vertical scrolling case seems like the right behavior, but that we shouldn't scroll anchor vertically if you're only horizontally scrolled.

I wonder, should we actually just only ever scroll anchor vertically?

Comment 7 by skobes@chromium.org, Sep 15 2016

Yeah it's probably fine to anchor only on the axis of the writing-mode.

Comment 9 by skobes@chromium.org, Sep 22 2016

Status: Fixed (was: Available)

Sign in to add a comment