MDN Drag and Drop example no longer works
Categories
(Core :: DOM: Copy & Paste and Drag & Drop, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox122 | --- | unaffected |
firefox123 | --- | unaffected |
firefox124 | --- | fixed |
People
(Reporter: handyman, Assigned: m_kato)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
The drag-and-drop example is here. mozregression puts the cause at bug 1586471. NI to :m_kato since you are the author. It blamed Part 4 for this (Fix drag threshold for mochitests), which is obviously nonsense... but something happened.
Assignee | ||
Updated•8 months ago
|
Assignee | ||
Comment 1•8 months ago
|
||
It depends on xorigin iframe. I guess that Part 1 fix causes this regression.
Comment 2•8 months ago
|
||
Set release status flags based on info from the regressing bug 1586471
Comment 3•8 months ago
|
||
(In reply to David Parks [:handyman] from comment #0)
It blamed Part 4 for this (Fix drag threshold for mochitests), which is obviously nonsense...
(That's just a bit of misleading output on mozregression's part. It always prints the last commit in the push, but the regression window applies to the push as a whole. We don't do CI builds for intermediate commits in a push that would allow mozregression to bisect commits within a push.)
Assignee | ||
Comment 4•8 months ago
|
||
Assignee | ||
Comment 5•8 months ago
|
||
This is a regression by bug 1586471.
We should use ReceiveInputEvent for all drag events on desktop.
Also, GV issue is bug 1878819 since we have to consider more when APZ
controller thread and main thread are different. But GV doesn't turn
on fission yet.
And, there is no way to add tests for native drag and drop operations.
S2 due to regressing something that's being taught on MDN. Please downgrade if S2 is too high.
Description
•