New issue
Advanced search Search tips

Issue 708655 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Apr 2017
Cc:
bokan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Dragging to the edge of a scrollable container no longer scrolls the container

Project Member Reported by jacobmorgan@google.com, Apr 5 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
Page with the bug: https://onlinesequencer.net/app/sequencer.php?frame=1
Click once on the grid to add a note, then drag it to the right edge of the window.

The basic structure of the page is an absolute-positioned viewport (#sequencer_main) with overflow:scroll which contains a larger <div> element (#sequencer_inner) with an absolute-positioned element for each note. The elements are dragged by updating their top: and left: properties.

I tried making a simple page with the same structure but couldn't reproduce the problem, I'll update if I can find a minimal test case. 

What is the expected behavior?
The outer container should scroll, in the same way as if you selected some text on this page and dragged it to the bottom of the window. It works in older Chrome versions and other browsers.

What went wrong?
Nothing happens.

Did this work before? Yes 56

Does this work in other browsers? Yes

Chrome version: 57.0.2987.133  Channel: stable
OS Version: OS X 10.12.3
Flash Version:

Comment 1 by schenney@chromium.org, Apr 5 2017

Components: Blink>Scroll
Labels: OS-Android OS-Chrome OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)
Confirmed that in M-58 on Linux we do not auto-scroll to keep the dragged element in frame. But should we?

Is this due to scroll anchoring or the like?

Comment 2 by bokan@chromium.org, Apr 6 2017

Cc: bokan@chromium.org
Status: WontFix (was: Untriaged)
Bisected this down to: https://chromium.googlesource.com/chromium/src/+/94c73aebe631326d3d09aed291a6c335040b5447

This was an intentional change. The example page has 'user-select: none' so we don't auto scroll as we generally don't want to autoscroll if the user drags over a non-selectable region. I'm guessing the current implementation of drag and drop here is custom. If you want autoscrolling you'll either have to make your element draggable so that Chrome knows this is actually a drag or implement your own autoscrolling by listening to mouse move events while you're performing a drag.

As an additional data point: Firefox also does not autoscroll in this case.

Closing as WontFix since this is WAI but feel free to followup if necessary.
►

Sign in to add a comment