Unable to start chrome with scroll-anchoring (flag) disabled
Reported by
bobby.er...@vtinfo.com,
Feb 13 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. Compile and run the java class 2. In the browser, check chrome://version 3. In the browser, check chrome://flags/#enable-scroll-anchoring What is the expected behavior? Chrome should start with #enable-scroll-anchoring set to Disabled What went wrong? Chrome starts with #enable-scroll-anchoring set to Default Did this work before? Yes 55.0.2883.75 Does this work in other browsers? Yes Chrome version: 56.0.2924.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0 This is obviously for automated testing. Scroll Anchoring in Chrome 56 breaks the JavaScript-based scrolling in our app. I originally posted this on the chromedriver bug list at https://bugs.chromium.org/p/chromedriver/issues/detail?id=1679. gmanikpure@chromium.org noted that chromedriver passed the flag through to chrome (chrome://version) and sent me here.
,
Feb 13 2017
about:flags defines it - https://cs.chromium.org/chromium/src/chrome/browser/about_flags.cc?type=cs&q=scroll-anchoring&l=1810 But no foo_switches.cc file defines the actual flag, so it is a no-op. It better just be removed.
,
Feb 13 2017
1. Thanks for the heads-up on overflow-anchor: none. 2. I'm not currently able to publish a link to our app, but I'll see what I can do. Hard to imagine their fixing it without being able to recreate it. 3. disable-blink-features=ScrollAnchoring does not set the flag, but scrolling behaves as if it's off. 4. It sounds like you mean that chrome://flags/#enable-scroll-anchoring does nothing. I don't think that's right.
,
Feb 13 2017
Oh, I misunderstood. If you manually specify the flag, the about:flags indication does not change. Is that the bug you are trying to report? If so, I believe this is by design. about:flags does not reflect the current state of the flag, it just reflects the current state of the about:flags entry.
,
Feb 13 2017
,
Feb 13 2017
I was asking for a way to turn off scroll-anchoring through chromedriver. If I disable the flag in chrome://flags and restart chrome, I get two symptoms: 1. chrome://flags/#enable-scroll-editing shows "Disabled" and 2. my scroll problem goes away But if I start chrome through chromedriver with --disable-scroll-anchoring, 1. chrome://flags/#enable-scroll-editing shows "Default" and 2. scroll problem persists Now, if I start chrome through chromedriver with --disable-blink-features=ScrollAnchoring, 1. chrome://flags/#enable-scroll-editing shows "Default" and 2. scroll problem goes away So what I was asking for (disable-scroll-anchoring) is met by disable-blink-features=ScrollAnchoring. I passed overflow-anchor along to my dev guys, and we're working on a stand-alone program that shows the error with scroll-anchoring.
,
May 15 2018
skobes@ - are you the right owner for this scroll anchoring related request?
,
May 15 2018
--disable-blink-features=ScrollAnchoring is the correct way to disable scroll anchoring from the command line. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by phistuck@chromium.org
, Feb 13 2017Labels: -Hotlist-Interop OS-Android OS-Chrome OS-iOS OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Summary: Remove the no-op scroll anchoring flag from about:flags (was: Unable to start chrome with scroll-anchoring (flag) disabled)