New issue
Advanced search Search tips
Starred by 5 users
Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Feature

Blocked on:
issue 416862



Sign in to add a comment
Allow websites to disable elastic scroll effects
Reported by kenneth....@gmail.com, Jan 9 2014 Back to list
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36

Steps to reproduce the problem:
1. Open twitter.com and log in
2. Scroll down
3. Observe elastic scroll on window interfering with infinite scroll

What is the expected behavior?
Elastic scroll would be disabled on this site.

What went wrong?
We'd like to disable elastic scroll, to remove the jarring clash between the infinite scroll and elastic scroll effect.

We might also use overscroll in the future for pull-to-refresh effects.

It's currently possible to remove this effect by using overflow:hidden on the html & body, and adding scroll to a wrapper div. However, this feels like a hack. Our library code is watching the window for scroll events.

Ideally, elastic scroll could be disabled with a CSS property or meta tag.

Did this work before? N/A 

Chrome version: 31.0.1650.63  Channel: stable
OS Version: OS X 10.9.1
Flash Version: Shockwave Flash 11.9 r900
 
Labels: -Type-Bug Type-Feature
Comment 2 by meh...@chromium.org, Jan 10 2014
Labels: Cr-Blink
Status: Untriaged
Thanks for the report. Is this possible in latest Webkit?
Not that I know of.
Comment 4 by meh...@chromium.org, Jan 10 2014
Could you please also open a report at bugs.webkit.org?

Please post the webkit bug number here then. Thanks.
Comment 6 by meh...@chromium.org, Jan 11 2014
Labels: WebKit-ID-126786
Thanks. 
Project Member Comment 7 by bugdroid1@chromium.org, Feb 14 2014
Labels: -WebKit-ID-126786 WebKit-ID-126786-NEW
https://bugs.webkit.org/show_bug.cgi?id=126786

Cc: bokan@chromium.org rbyers@chromium.org
Labels: -Cr-Blink Cr-Blink-Scroll
Comment 9 by rbyers@chromium.org, Nov 27 2015
Blockedon: chromium:416862
Cc: ccameron@chromium.org
Labels: -Pri-2 Pri-3 Hotlist-Input-Dev
Status: Available
This is a scenario that should be possible with our proposed scroll customization API  (issue 416862).  If other browsers wanted to push a specific simple CSS property for this, we'd probably be willing to implement it, but at the moment our focus is on exposing underlying primitives that enable frameworks to have much more control.  I would have a hard time justifying the standardization effort for something which (for us) is a Mac-specific scenario.
Cc: tdres...@chromium.org
There are a bunch of different behaviors that are triggered by overscrolling the root:
- pull to refresh
- overscroll glow
- rubber-banding
- url bar hiding

Pull to refresh will only give you a way to disable all of these, not each one individually. If we want to enable cases where you prevent rubber-banding, but still allow URL bar hiding for example, we'll need an explicit API.
You mean scroll customization will only give you a way to disable all of these?  That's fair.  Although on Mac there's only rubber-banding (so worst case someone can do this with a platform check).  We are probably adding an explicit p2r API for Android, so I guess that's a good argument that this sort of API makes sense along WITH scroll customization.

Anyway I'm not opposed to an explicit API here, but I wouldn't put pushing for it with the other vendors very high on my priority list personally.

Sorry, yes, I meant scroll customization...

I agree that we don't need to prioritize this very highly.
Owner: majidvp@chromium.org
Status: Assigned
I believe majidvp@ is currently working on something that should address this. Majid, feel free to dup into an existing bug if appropriate.
This can be done as an extension to 'overscroll-action' property which is proposed here [1]. 

We have explicitly called out such effects to be out-of-scope for that proposal in order to focus on pull-to-refresh and swipe navigation usecases mainly because those can be very disruptive to UX and because there was no apparent interest from other vendors for this. But, it will be a simple extension to that e.g.,

#scroller {
  overscroll-action: no-navigation no-cosmetic-effect 
}

   

[1] https://discourse.wicg.io/t/proposal-api-to-control-user-gesture-navigation/1536/12
Sign in to add a comment