Closed
Bug 1492196
Opened 7 years ago
Closed 7 years ago
Fix focus-related race conditions in browser_searchbar_openpopup.js
Categories
(Firefox :: Search, enhancement, P1)
Firefox
Search
Tracking
()
RESOLVED
FIXED
Firefox 64
| Tracking | Status | |
|---|---|---|
| firefox64 | --- | fixed |
People
(Reporter: Gijs, Assigned: Gijs)
References
Details
Attachments
(1 file)
In the drop_opens_popup.js, we attempt to simulate a drag from "somewhere else" to the search bar, and test whether the drop causes the popup to appear.
Unfortunately, the drag manager code ( https://searchfox.org/mozilla-central/rev/6c82481caa506a240a626bb44a2b8cbe0eedb3a0/dom/events/EventStateManager.cpp#1837-1846 ) bails out of generating a drag (from the mousedown + mousemove events that EventUtils.js generates) if there's a selection frame that it thinks might be handling dragging. Because the previous test focuses the URL bar, sometimes that happens here and breaks the test, especially after flipping the uriIsAboutBlank switch in bug 1362774.
| Assignee | ||
Updated•7 years ago
|
Assignee: nobody → gijskruitbosch+bugs
Status: NEW → ASSIGNED
Component: General → Search
Priority: -- → P1
Comment 1•7 years ago
|
||
This test is the last orange I'm seeing with <searchbar> converted to a CE. I don't think this race is the reason, but going to keep an eye on this anyway.
See Also: → 1460982
| Assignee | ||
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
Comment on attachment 9010008 [details]
Bug 1492196 - fix browser_searchbar_openpopup.js so we don't accidentally try to drag content in the URL bar, r?florian
Florian Quèze [:florian] has approved the revision.
Attachment #9010008 -
Flags: review+
Pushed by gijskruitbosch@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/bda9ea2048f2
fix browser_searchbar_openpopup.js so we don't accidentally try to drag content in the URL bar, r=florian
Comment 5•7 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 64
You need to log in
before you can comment on or make changes to this bug.
Description
•