Scrolling behaviour whilst dragging an element not as expected using HTML5 drag API
Reported by
sypher1...@gmail.com,
Sep 14 2017
|
|||||||
Issue descriptionChrome Version : Version 61.0.3163.79 (Official Build) (64-bit) URLs (if applicable) : https://plnkr.co/edit/q8UUlReWYQfn4PybCX0U?p=preview Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Firefox: PASS (55.0.3 (32-bit)) What steps will reproduce the problem? (1)Scroll down to bring a scrollable div into view that was previously off screen. (2)Click and start dragging a draggable element. (3)Move the mouse to the bottom of a scrollable div that initially loads off the viewable area. What is the expected result? The div should scroll down. What happens instead? The div does not scroll. Please provide any additional information below. Attach a screenshot if possible. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Sep 15 2017
Tested the issue on reported version Stable 61.0.3163.79, Latest Canary 63.0.3216.0 using Ubuntu 14.04, Windows 7 and Mac 10.12.1. This issue is seen from M50 and is a Non-Regression issue. Hence marking it as untraiged for further inputs on this.
,
Sep 19 2017
,
Sep 19 2017
,
Sep 28 2017
Able to repro. Weird. Sandra, something to take a look at related to autoscrolling.
,
Aug 21
I was not able to reproduce on Chrome Canary 70.0.3528.0 on MacOS. For both examples in the link provided (https://plnkr.co/edit/q8UUlReWYQfn4PybCX0U?p=preview), dragging the draggable items successfully caused the div to scroll both when dragged to the top and when dragged to the bottom.
,
Aug 21
The original repro steps now work correctly for me too, Windows 68.0.3440.106. sypher1987@: Can you still reproduce in the latest version of Chrome?
,
Sep 4
The NextAction date has arrived: 2018-09-04
,
Sep 4
Closing since it appears this no longer repros. Feel free to reply if otherwise and we can reopen.
,
Sep 6
Sorry for the delay, I have re-tested this myself and it is indeed now fixed. Thanks very much for addressing this and responding. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ligim...@chromium.org
, Sep 14 2017