Closed
Bug 1438097
Opened 7 years ago
Closed 7 years ago
nsXBLWindowKeyHandler should wait reply from remote process even if the keyboard event won't be fired on content in the default event group
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P2)
Core
DOM: UI Events & Focus Handling
Tracking
()
RESOLVED
FIXED
mozilla60
Tracking | Status | |
---|---|---|
firefox60 | --- | fixed |
People
(Reporter: masayuki, Assigned: masayuki)
References
Details
Attachments
(1 file)
Currently, nsXBLWindowKeyHandler::HandleEventOnCaptureInSystemEventGroup() doesn't wait reply for keyboard events which won't be fired on content in the default event group (i.e, its mFlags.mOnlySystemGroupDispatchInContent is true). This is reasonable if system event listeners in remote process won't consume any keyboard events before nsXBLWindowKeyHandleor. However, it may not be so.
So, nsXBLWindowKeyHandler::HandleEventOnCaptureInSystemEventGroup() should mark such events as "wants reply from remote process".
Assignee | ||
Comment 1•7 years ago
|
||
Assignee | ||
Comment 2•7 years ago
|
||
Updated•7 years ago
|
Priority: -- → P2
Comment hidden (mozreview-request) |
Comment 4•7 years ago
|
||
mozreview-review |
Comment on attachment 8951156 [details]
Bug 1438097 - nsXBLWindowKeyHandler::HandleEventOnCaptureInSystemEventGroup() should mark keyboard events which won't be fired on content in the default event group as "wait reply from remote process"
https://reviewboard.mozilla.org/r/220422/#review226450
Attachment #8951156 -
Flags: review?(bugs) → review+
Pushed by masayuki@d-toybox.com:
https://hg.mozilla.org/integration/autoland/rev/c25eaa199ff8
nsXBLWindowKeyHandler::HandleEventOnCaptureInSystemEventGroup() should mark keyboard events which won't be fired on content in the default event group as "wait reply from remote process" r=smaug
![]() |
||
Comment 6•7 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla60
Updated•6 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•