Middle-clicking links on DuckDuckGo search result triggers popup blocker
Categories
(Core :: DOM: Core & HTML, defect, P2)
Tracking
()
People
(Reporter: saschanaz, Assigned: edgar)
References
(Depends on 1 open bug)
Details
Attachments
(2 files)
- Open https://duckduckgo.com/?t=ffab&q=mozilla&ia=web
- Middle-click the description part, not the title of the search results
Expected: A tab should be opened
Actual: The popup blocker prevents it
Reporter | ||
Comment 1•4 years ago
|
||
Hey Emilio, I saw your recent work on transient activation, is this something still interests you?
Comment 2•4 years ago
|
||
This is because duckduckgo is opening the window on a mousedown
event. The popup blocker in GetEventPopupControlState
determines that mousedown isn't allowed to open the popup (see the popup_allowed_events
pref), and thus blocks it.
So in order to fix it we could add mousedown
to the events, or duckduckgo
could change their event handler to use click
or mouseup
.
Olli, Masayuki, do you have context on why we block popups on mousedown
? I guess it could be annoying if we allowed it on the primary button because it could prevent selection or something, but other than that, for middle-click at least it probably should be allowed?
Comment 3•4 years ago
|
||
I don't know.
But according to UserActivation.cpp
, mousedown
is treated as a user activating action. So, it seems that popup blocker should also allow it.
Edgar?
Assignee | ||
Comment 4•4 years ago
|
||
I guess we could at least allow popup for mousedown on middle-button.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
And add more tests for different button value.
Assignee | ||
Comment 6•4 years ago
|
||
We allow popups on middle button for mouse events, pointer event should just be
consistent with mouse event.
Depends on D101507
Assignee | ||
Comment 7•4 years ago
|
||
Comment 9•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/2ff2125f9ab0
https://hg.mozilla.org/mozilla-central/rev/3d3c6b9521dc
Comment 10•4 years ago
|
||
bugherder |
Updated•4 years ago
|
Comment 11•4 years ago
|
||
Successfully reproduced the issue on Firefox 86.0a1 (2021-01-11) under macOS 10.15.7 following the steps from Comment 0.
The issue is fixed on latest Nightly 87.0a1 (2021-02-03) and Firefox 86.0b5. Tests were performed on macOS 10.15.7, Ubuntu 20.04 and Windows 7.
Description
•