Closed
Bug 1376849
Opened 7 years ago
Closed 3 years ago
Investigate why AsyncEventDispatcher is sometimes unlabeled
Categories
(Core :: DOM: Core & HTML, defect, P3)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: billm, Unassigned)
References
Details
It's not uncommon for AsyncEventDispatcher to be unlabeled. One way I could imagine this happening is if someone calls NS_DispatchToMainThread directly on the dispatcher rather than calling PostDOMEvent.
The other way is if PostDOMEvent is somehow unable to find a DocGroup to use.
|
||
Updated•7 years ago
|
Priority: -- → P1
|
||
Updated•7 years ago
|
Priority: P1 → P2
|
||
Comment 1•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
|
Assignee | |
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
|
||
Updated•3 years ago
|
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•