Open
Bug 964156
Opened 12 years ago
Updated 3 years ago
Composition offset into TabParent may be incorrect
Categories
(Core :: DOM: Events, defect)
Tracking
()
NEW
People
(Reporter: m_kato, Assigned: m_kato)
References
Details
Original implementation of e10s IME was for old Android fennec. Android's implementation for IME always use NS_SELECTION_SET to mark composition string.
NS_SELECTION_SET notices NOTIFY_IME_OF_SELECTION_CHANGE, then, PuppetWidget will update a cache into tab parent. So it was OK for android's widget.
But when dispatching composition event (or text event), gecko don't notice NOTIFY_IME_OF_SELECTION_CHANGE.
so we should use composition update event to notice composition start offset and etc.
| Assignee | ||
Comment 1•12 years ago
|
||
TabParent calculates start offset and tareget offset by complex way, so this isn't simple. And selection change event will be called event if non-IME.
This IPC for IME offset should be used by IME only.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•