Closed
Bug 329310
Opened 19 years ago
Closed 19 years ago
Can't type characters with second byte 0D in Gmail Google Talk
Categories
(Camino Graveyard :: HTML Form Controls, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
Camino1.5
People
(Reporter: markpeak, Assigned: mikepinkerton)
References
()
Details
Attachments
(1 file)
22.43 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060214 Camino/1.0
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060214 Camino/1.0
In new Google Talk web interface in Gmail. Typing Thai character "Yo Ting" (Unicode 0E0D) will be converted to Enter (which means send that chat message).
This problem isn't occurred on Firefox 1.5 on the same OSX machine.
Reproducible: Always
Steps to Reproduce:
1. Sign up for Gmail and Google Talk
2. Enable chat via Gmail
3. Clicking on some buddy name
4. Type "Yo Ying"
Actual Results:
The message is sent (without Yo Ying)
Expected Results:
"Yo Ying" should display as normal character
Comment 1•19 years ago
|
||
Confirmed!
"Yo Ying" = ญ
Does this happen if you use the Unicode Hex Input keyboard layout (opt+codepoint), or just the Thai layout? How about copy-paste?
ญ
Blocks: 313841
Component: Page Layout → HTML Form Controls
Reporter | ||
Comment 3•19 years ago
|
||
Unicode Hex Input produces same result, also as onscreen keyboard viewer.
But copy-paste works fine.
Comment 4•19 years ago
|
||
Confirmed #3
Sam followed up a hunch I had and we've mostly determined the cause of this bug. 0D is hex for carriage return. In addition to the Thai character Yo Ying, we got "box drawings down light and right heavy" (Ux250D,┌) to cause the same behavior using the Unicode Hex Input keyboard layout.
I don't know if our Cocoa-Gecko-TSM IME conversion is getting lost somewhere along the way and sending 0D instead of completely composing the character, or if Google is doing some trapping (although that seems unlikely, given this works in Fx), or what, but I think we've sufficiently narrowed down the bug to confirm it and to give someone an avenue for investigation.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Can't type some Thai characters in Gmail Google Talk → Can't type characters with second byte 0D in Gmail Google Talk
Comment 6•19 years ago
|
||
Show "Yo Ying" in
Unicode = 0E0D
UTF-8 = 0E B8 8D
Comment 7•19 years ago
|
||
Comment on attachment 214816 [details]
Mac OS X 10.4.5 Yo Ying Charactor Palette
Yo Ying = �
Updated•19 years ago
|
Target Milestone: --- → Camino1.1
Comment 8•19 years ago
|
||
Does this happen only on Google pages, or any page? Can someone make a simple textcase and attach it?
Comment 9•19 years ago
|
||
(In reply to comment #8)
> Does this happen only on Google pages, or any page? Can someone make a simple
> textcase and attach it?
>
It's not "Google pages", but simply this Gmail Chat textarea. When saving the page for offline viewing, I can't duplicate the issue.
Something in Gmail's code must be looking for that 0D and translating it as "return".
I can't create a testcase since this code is highly dependent on code that I don't understand (mostly JavaScript). I have no way to know how to replicate the page as it obviously isn't just a simple <textarea>.
Reporter | ||
Comment 10•19 years ago
|
||
>It's not "Google pages", but simply this Gmail Chat textarea. When saving the
page for offline viewing, I can't duplicate the issue.
Since Thai is included in OSX already, I think you can easily setup the environment same as mine
- System Preferences > International > Input Menu and enable "Thai" (not Thai-Pattachote)
- Go to Google Talk web chat and switch keyboard layout to Thai
- The keymap is the same one as capital "P"
Anyway, I'll try to create testcase.
Reporter | ||
Comment 11•19 years ago
|
||
I test this on 1.1 nightly build 2006070101, the problem is gone. Please close this bug.
Comment 12•19 years ago
|
||
Yeah, this WFM using a branch nightly from 5/25. Google must have fixed something on their end. Closing this as WFM.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•