Closed GoogleCodeExporter closed 9 years ago
Accepting. A similar problem is reported with accented characters, which likely
has the same root cause. I'm treating this as a blocker.
Original comment by classi...@floodgap.com
on 17 Jun 2014 at 1:17
Cut and paste works: ありがとう
So this is likely something with IME. I suspect bug 965685.
Original comment by classi...@floodgap.com
on 18 Jun 2014 at 3:37
In a debug build, trying to type あ, we get this naughty assertion:
2014-06-17 21:05:59.901 firefox[2512] ****in sendCompositionEvent; type = 2200
2014-06-17 21:05:59.910 firefox[2512] ****in sendTextEvent; string =
'あ{NSUnderline = 2; NSUnderlineColor = NSCalibratedWhiteColorSpace 0.17 1; }'
2014-06-17 21:05:59.910 firefox[2512] markRange = 0, 1; selRange = 1, 0
2014-06-17 21:05:59.910 firefox[2512] ****in underlineAttributeToTextRangeType
= 2
Assertion failure: mLastData == aTextEvent->theText (The text of a text event
must be same as previous data attribute value of the latest compositionupdate
event), at
/Volumes/BruceDeuce/src/mozilla-31b/dom/events/TextComposition.cpp:160
So this pretty clearly implicates IME.
Original comment by classi...@floodgap.com
on 18 Jun 2014 at 4:07
The old 29 code used an array of CountRanges(aString) + 1. This looks like an
artifact of how the array was constructed. Adding 1 to CountRanges makes no
difference. So the problem is something about sendTextEvent:.
Original comment by classi...@floodgap.com
on 18 Jun 2014 at 4:45
We're not setting .data in the WidgetCompositionEvent. This is going to be a
little tricky.
Original comment by classi...@floodgap.com
on 18 Jun 2014 at 4:51
Rewriting our nsChildView.mm IME code to include analogous changes to
https://hg.mozilla.org/releases/mozilla-aurora/rev/8d48a0f50b4c seems to fix
the assertion and text seems to function correctly for (tested) Japanese,
German and Spanish, so it probably all works.
Original comment by classi...@floodgap.com
on 20 Jun 2014 at 3:48
Korean input came back to normal on 31.0b2.
Original comment by bws...@gmail.com
on 21 Jun 2014 at 5:52
Excellent. Thanks for the report. We will consider this ...
Original comment by classi...@floodgap.com
on 21 Jun 2014 at 6:00
Original issue reported on code.google.com by
bws...@gmail.com
on 17 Jun 2014 at 9:57