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

Issue 592432 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Scroll Blocked First time in cafe.daum.net

Reported by sujith...@samsung.com, Mar 7 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36

Steps to reproduce the problem:
1. goto cafe.daum.net/WorldcupLove
2. select PC version
3. zoomin and try to scroll left/right

What is the expected behavior?
first scroll not working

What went wrong?
scroll should work properly.

Did this work before? N/A 

Chrome version: 48.0.2564.95  Channel: n/a
OS Version: 
Flash Version: Shockwave Flash 19.0 r0

If we block the return statement code issue not seen.

void LayerImpl::DistributeScroll(ScrollState* scroll_state) {
   .
   .
   .

   if (!scroll_state->should_propagate() &&
      scroll_state->delta_consumed_for_scroll_sequence() &&
      scroll_state->current_native_scrolling_layer() != this) {
     return;
  }
 
demo.mp4
3.6 MB Download
Cc: aelias@chromium.org majidvp@chromium.org tdres...@chromium.org
Status: WontFix (was: Unconfirmed)
If you make the html element of the first frame in the frameset overflow:hidden, then this issue goes away.

The problem is that we end up locking the scroll to a scroller that can't scroll very far.

The same thing happens with touchpad scroll in Safari. Marking WontFix, since this is a site design problem.

Earlier chrome version like V45, we observed its working fine with current content. And same content on V48 behavior is broken. This is how its intended to work ?
This is due to https://bugs.chromium.org/p/chromium/issues/detail?id=526462, which caused touch scrolling to latch to a single scroller for the duration of the scroll.

It's unfortunate that we're hitting compatibility issues here, but this is the first issue I've seen, and it's also broken in Safari, so I think we're safe to consider this a bug with the site.
We tried to reproduce the issue in ipad safari, but issue is not reproducible there. 
Attached video and useragent details.

20160309_163657.mp4
3.0 MB Download
20160309_164504.jpg
3.2 MB View Download
It's broken for touchpad scrolling in Safari.
ok. i was comparing normal touch scroll scenario in chrome and safari in tablet devices. In that chrome latest is broken, but safari is working fine.
Yeah, to repro in Safari, you need a non-mobile device, with a touchpad.
Cc: kphanee@chromium.org
I believe the intention of removing chaining was to have a compatible behavior with safari. So, if mobile safari is supporting the scroll (by chaining or otherwise) , shouldn't chrome on mobile also support this scroll?
Cc: rbyers@chromium.org
Oh, sorry.

Mobile Safari also performs touch scroll latching (Use http://jsbin.com/cavera) as an example.

The reason this isn't broken on mobile Safari is that on mobile Safari iframes aren't scrollable (https://bugs.webkit.org/show_bug.cgi?id=149264). This avoids the problem by not having the nested scrollers that are causing this to misbehave.

Sign in to add a comment