Closed
Bug 1374921
Opened 8 years ago
Closed 7 years ago
DOM Event handlers should not use QI from nsIDOMEvent
Categories
(Core :: DOM: Events, defect, P2)
Core
DOM: Events
Tracking
()
RESOLVED
FIXED
mozilla61
Tracking | Status | |
---|---|---|
firefox61 | --- | fixed |
People
(Reporter: masayuki, Assigned: bzbarsky)
References
Details
Although this does not affect any benchmarks because of event handlers' performance issue, I guess that this may affect quickness of user operation.
https://searchfox.org/mozilla-central/search?q=nsIDOM.*Event%3E.*%5Cn%3F.*do_QueryInterface&case=false®exp=true&path=
I think that if all of them can use Widget*Event instead, they should use it. Otherwise, I think that mozilla::dom::*Event classes should have |As*Event()| virtual methods like Widget*Event.
Comment 1•8 years ago
|
||
Probably yes, though need to be careful with this. What if we want to handle also events named foo when those aren't dispatched using WidgetFooEvent, but generic WidgetEvent. In that case event's message would be the generic one.
Updated•8 years ago
|
Priority: -- → P2
![]() |
Assignee | |
Comment 2•7 years ago
|
||
I believe the patches landed for bug 1455055 pretty much fix this. Masayuki-san, do you agree?
Flags: needinfo?(masayuki)
Reporter | ||
Comment 3•7 years ago
|
||
(In reply to Boris Zbarsky [:bz] (no decent commit message means r-) from comment #2)
> I believe the patches landed for bug 1455055 pretty much fix this.
> Masayuki-san, do you agree?
Yes, I do! Really thank you for your work!!
Assignee: nobody → bzbarsky
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(masayuki)
Resolution: --- → FIXED
Reporter | ||
Updated•7 years ago
|
status-firefox61:
--- → fixed
Target Milestone: --- → mozilla61
You need to log in
before you can comment on or make changes to this bug.
Description
•