Closed
Bug 1260220
Opened 9 years ago
Closed 2 years ago
Links and images appear far away from mouse pointer when I drag them on http://infox.sg/
Categories
(Core :: DOM: Copy & Paste and Drag & Drop, defect)
Core
DOM: Copy & Paste and Drag & Drop
Tracking
()
RESOLVED
DUPLICATE
of bug 941356
Tracking | Status | |
---|---|---|
firefox48 | --- | affected |
People
(Reporter: arni2033, Unassigned)
References
Details
(Keywords: parity-chrome, Whiteboard: btpp-backlog)
Attachments
(1 file)
517.49 KB,
image/png
|
Details |
>>> My Info: Win7_64, Nightly 48, 32bit, ID 20160326030430
STR_1:
1. Open http://infox.sg/
2. Hover mouse over any image in the 1st block of news (inside the element ".layout-1")
3. Hold left mouse button, then move mouse by 50px to the bottom to start drag-n-drop
STR_2:
1. Open the following "data:" url or click URL in the form above
> data:text/html,<div style="transform: translateX(400px);"><a>asdf
2. Select "asdf" on the page, hover mouse over "asdf"
3. Hold left mouse button, then move mouse by 50px to the bottom to start drag-n-drop
STR_3:
1. Open the following "data:" url or click URL in the form above
> data:text/html,<div style="transform: translateX(400px);"><a><img src="about:logo">
2. Hover mouse over image
3. Hold left mouse button, then move mouse by 50px to the bottom to start drag-n-drop
AR: Links and images appear far away from mouse pointer
ER: Links and images should appear directly under mouse pointer
Comment 2•9 years ago
|
||
The element likely has a transform applied to it, making this a case of 467297.
(In reply to Neil Deakin from comment #2)
> The element likely has a transform applied to it, making this a case of 467297.
This bug should stay separate, as it says precisely, "Elements should appear directly under pointer"
This is indeed a part of bug 467297 BUT the point is that bug 467297 is a deadlock; it couldn't be closed if somebody decided to fix some part of it (e.g. the part described in this bug). It asks for
ALL transforms to be preserved at the same time. That's too much. Even GoogleChrome doesn't do that.
// The same applies for (irrelevant) bug 455164.
I think it's wrong to use existance of 467297 as an excuse for this bug 1260220. All transforms should
be considered separately, but translates should be at the beginning of the list. That's my opinion.
Updated•9 years ago
|
Whiteboard: [parity-Chrome] → [parity-Chrome] btpp-backlog
Comment 4•7 years ago
|
||
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-chrome
Whiteboard: [parity-Chrome] btpp-backlog → btpp-backlog
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•