Closed
Bug 1107617
Opened 10 years ago
Closed 10 years ago
add WritingMode to the NotifyIMESelection message
Categories
(Core :: DOM: Content Processes, defect)
Core
DOM: Content Processes
Tracking
()
RESOLVED
FIXED
mozilla37
People
(Reporter: jfkthame, Assigned: jfkthame)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
9.78 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
The arrow-key remapping patches in bug 1077515 depend on adding a WritingMode to the reply to the NS_QUERY_SELECTED_TEXT event. However, this doesn't work under e10s.
To fix this, we can cache the writing mode on the TabParent at the same time as updating the focus (caret position) via the NotifyIMESelection event.
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8532160 -
Flags: review?(bugs)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → jfkthame
Status: NEW → ASSIGNED
Updated•10 years ago
|
Attachment #8532160 -
Flags: review?(bugs) → review+
Comment 2•10 years ago
|
||
Assuming ParamTraits<mozilla::WritingMode> actually does what it tries to (and it should if the code compiles).
Comment 3•10 years ago
|
||
Comment on attachment 8532160 [details] [diff] [review]
Add support for writing-mode to the NotifyIMESelection message
Hmm, it is not clear to me why
WriteParam(aMsg, aParam.mWritingMode); and return ReadParam(aMsg, aIter, &aResult->mWritingMode); actually work.
Why don't you need to read/write the internals of the class
Attachment #8532160 -
Flags: review+ → review?(bugs)
Comment 4•10 years ago
|
||
Comment on attachment 8532160 [details] [diff] [review]
Add support for writing-mode to the NotifyIMESelection message
Oh, silly me. WritingMode is just a bit odd class, well naming in it is.
WritingMode has member variable mWritingMode.
Attachment #8532160 -
Flags: review?(bugs) → review+
Assignee | ||
Comment 5•10 years ago
|
||
Target Milestone: --- → mozilla37
Comment 6•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•