Closed
Bug 1976609
Opened 1 year ago
Closed 1 year ago
Make popupshowing event hold the event that triggered it
Categories
(Core :: XUL, task)
Core
XUL
Tracking
()
RESOLVED
FIXED
142 Branch
| Tracking | Status | |
|---|---|---|
| firefox142 | --- | fixed |
People
(Reporter: daisuke, Assigned: daisuke)
References
Details
(Whiteboard: [sng])
Attachments
(1 file)
We sometimes wanted to know the event that triggered the popupshowing event.
We have encountered the same situation again.
After discussing with :masayuki, we will support a triggered event type field in popupshowing event.
https://phabricator.services.mozilla.com/D255955#inline-1409421
| Assignee | ||
Comment 2•1 year ago
|
||
Oh, thanks!
| Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
Attachment #9499966 -
Attachment description: WIP: Bug 1976609: popupshowing event holds trigger event type → Bug 1976609: popupshowing event holds trigger event type
Updated•1 year ago
|
Attachment #9499966 -
Attachment description: Bug 1976609: popupshowing event holds trigger event type → Bug 1976609: popupshowing event holds an event that triggered it
| Assignee | ||
Comment 4•1 year ago
|
||
I'm sorry. Event type was not enough for our purpose, and we needed to see the event target.
Thus, as same to XULCommandEvent.sourceEvent, I want to make popupshowing event needs to hold an event that triggered it.
Summary: Make popupshowing event hold the event type triggered → Make popupshowing event hold the event that triggered it
Updated•1 year ago
|
Whiteboard: [sng]
Updated•1 year ago
|
Pushed by dakatsuka.birchill@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/80a45d8977a8
https://hg.mozilla.org/integration/autoland/rev/f007341124a9
popupshowing event holds an event that triggered it r=webidl,masayuki,smaug
Comment 6•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox142:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 142 Branch
Updated•1 year ago
|
QA Whiteboard: [qa-triage-done-c143/b142]
You need to log in
before you can comment on or make changes to this bug.
Description
•