New issue
Advanced search Search tips

Issue 629322 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Jul 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Drag ghost image always slightly off from the place of touch

Reported by zla...@gmail.com, Jul 18 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Steps to reproduce the problem:
1. Go to http://jsfiddle.net/w96zgafv/ . (It's a simplest use of native drag & drop for positioning an element, based on http://stackoverflow.com/questions/2438320/html5-dragover-drop-how-get-current-x-y-coordinates )
2. Drag the element with mouse and observe how one cannot use the ghost image as a guide to the position where the image will land on drop.
3. Compare with Firefox and see how it works perfectly.

The amount of the miss is proportional to the place of the first touch event, i.e. it'll be more when clicked closer to the bottom right cornet.

A same 'off by a bit' behavior also happens when using event.dataTransfer.setDragImage(someElement,x,y) - the x,y offset are actually still affected subtracted by this quirky offset.

What is the expected behavior?
The ghost image should be rendered in a position that is stable relatively to the point of click or offset passed to setDragImage.

What went wrong?
The ghost image was rendered off by a varying amount.

Did this work before? No 

Chrome version: 51.0.2704.106  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0
 

Comment 1 by zla...@gmail.com, Jul 23 2016

I have tested this with 5 machines now and can see that for many it doesn't occur.

Two systems that it did occur in were both Dell Inspiron laptops (different models), both on Windows 10
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 24 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment