Open Bug 1161904 Opened 9 years ago Updated 3 years ago

PuppetWidget->DispatchInputEvent() triggers nsIEditorObserver callback asynchronously when running in content process

Categories

(Core :: DOM: Events, defect, P5)

Product:
Core
Component:
DOM: Events
Type:
defect

Tracking

()

People

(Reporter: timdream, Unassigned)

References

Details

STR:

1. Apply https://bugzilla.mozilla.org/attachment.cgi?id=8599697, which dispatches keyboard events from nsITextInputProcesser.
2. Go to any oop app and try to trigger an event from keyboard API.

Expected:

The |EditAction| callback on Line 385 of forms.js is run synchronously as the nTIP.keydown() event.

Actual:

It is being invoked asynchronously.

Note:

I am told to file a bug if there is a difference in behavior between inproc and oop, but obviously this can be a behavior we decide not to change. If so we should make the callback in chrome process filed asynchronously as well, and find some other way to solve bug 1137557 comment 16 in forms.js in that bug.
(I am pointing this bug to widget->DispatchInputEvent() because of finding in bug 1137557 comment 20)
Summary: widget->DispatchInputEvent() triggers nsIEditorObserver callback asynchronously when running in content process → PuppetWidget->DispatchInputEvent() triggers nsIEditorObserver callback asynchronously when running in content process

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.

Severity: normal → S4
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.