Closed
Bug 1693577
Opened 4 years ago
Closed 4 years ago
Fallback menupopup for input elements should include a triggerNode
Categories
(Toolkit :: General, defect, P3)
Toolkit
General
Tracking
()
RESOLVED
FIXED
89 Branch
People
(Reporter: TbSync, Assigned: TbSync)
References
Details
Attachments
(1 file)
In
https://hg.mozilla.org/mozilla-central/file/tip/toolkit/content/editMenuOverlay.js#l96
a fallback menupopup is added and used for a few input elements. The menupopup is
opened by calling
popup.openPopupAtScreen(e.screenX, e.screenY, true);
That call is not passing on the original event and therefore the target element of the resulting popupshowing
event does not have a triggerNode.
Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Severity: -- → S3
Priority: -- → P3
Pushed by dtownsend@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6a1d778a6cdf
Pass on original event to inluce triggerNode in popupshowing event. r=mossop
Comment 3•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox89:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 89 Branch
Comment 4•4 years ago
|
||
Since the status are different for nightly and release, what's the status for beta?
For more information, please visit auto_nag documentation.
status-firefox88:
--- → ?
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
I am fine with setting it to wontfix for beta and esr.
Updated•4 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•