Closed
Bug 642140
Opened 14 years ago
Closed 14 years ago
nsEventDispatcher should dispatch chrome only events to TabChildGlobal
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: smaug, Assigned: smaug)
References
Details
Attachments
(3 files)
9.97 KB,
patch
|
Details | Diff | Splinter Review | |
2.08 KB,
patch
|
jst
:
review+
|
Details | Diff | Splinter Review |
3.58 KB,
patch
|
Details | Diff | Splinter Review |
With this change using NS_EVENT_FLAG_ONLY_CHROME_DISPATCH does the right thing,
IMO, which is that the event is also dispatched to tabglobal.
We could even add a helper method to nsIPrivateDOMEvent to set that flag,
if needed.
Will upload to tryserver
Assignee | ||
Comment 1•14 years ago
|
||
Apparently there is still something wrong with the patch.
Assignee | ||
Comment 2•14 years ago
|
||
Bah, DispatchChromeEvent isn't quite like NS_EVENT_FLAG_ONLY_CHROME_DISPATCH.
The first one dispatched to chrome event handler, the latter one
just makes sure the event isn't dispatched to content.
Assignee | ||
Comment 3•14 years ago
|
||
Need to do just this for now, and I'll then file a followup to figure out
if we should change DispatchChromeEvent.
Attachment #519709 -
Flags: review?(jst)
Comment 4•14 years ago
|
||
Comment on attachment 519709 [details] [diff] [review]
simpler
r=jst. Any way we can test this?
Attachment #519709 -
Flags: review?(jst) → review+
Assignee | ||
Comment 5•14 years ago
|
||
There is a hackish way, I think, using a drop event and dragSession.
I'll write the test before pushing.
Assignee | ||
Comment 6•14 years ago
|
||
Assignee | ||
Comment 7•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•