Closed Bug 1179122 Opened 5 years ago Closed 5 years ago
Composition should manage target in parent process even when its child process has focus
Currently, EventStateManager sends composition events to TabParent. Therefore, TextComposition is now created only in the process which has composition actually. But this causes a lot of bugs which are detected by |Assertion failure: aCompositionEvent->message == (2200)| since if TabParent becomes deactive during a composition, WidgetCompositionEvent is dispatched to different content in the parent. For preventing this issue, TextComposition should guarantee that all composition events are sent to same TabParent.
See comment 0 for the detail. Although, even with this patch, I sometimes see hitting the assertion. Sigh... (Of course, this actually fixes some cases of that, though.)
Attachment #8628577 - Flags: review?(bugs)
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.