Open Bug 1181501 Opened 9 years ago Updated 3 years ago

eKeyPress event should be fired in XP level and dispatched with preceding eKeyDown event in same event loop

Categories

(Core :: DOM: UI Events & Focus Handling, enhancement, P3)

Product:
Core
Component:
DOM: UI Events & Focus Handling
Type:
enhancement

Tracking

()

Tracking Flags:
Tracking Status
e10s + ---

People

(Reporter: masayuki, Unassigned)

References

(Blocks 1 open bug)

Details

Currently, NS_KEY_DOWN and NS_KEY_PRESS are dispatched from widget separately. However, this causes hacky handling of preventDefault() of keydown event.
http://mxr.mozilla.org/mozilla-central/source/dom/ipc/TabChild.cpp?rev=e17e313a3066&mark=2544-2549#2539

I think that NS_KEY_DOWN_PRESS should be created and widget should dispatch it with enough information for dispatching both keydown event and keypress event.

Then, we can make better consistency between platforms and reduce number of IPC.

I think that we should fix this bug only with TextEventDispatcher here. Then, fixing bug 1137560 will fix this bug on all platforms automatically.
Version: 40 Branch → Trunk
Priority: -- → P3
Summary: [e10s] NS_KEY_PRESS event should be fired in XP level → [e10s] eKeyPress event should be fired in XP level
Component: Event Handling → User events and focus handling
Assignee: masayuki → nobody
Severity: normal → S3
Type: defect → enhancement
Summary: [e10s] eKeyPress event should be fired in XP level → eKeyPress event should be fired in XP level and dispatched with preceding eKeyDown event in same event loop
You need to log in before you can comment on or make changes to this bug.