Tibetan Unicode does not compose properly on MacOSX w/ built-in Tibetan - Wylie keyboard
Reported by
chris.j....@gmail.com,
Nov 7 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Example URL: https://www.tbrc.org Steps to reproduce the problem: 1. on MacOS 10.12.6 visit www.tbrc.org (or this site) 2. switch to MacOS builtin Tibetan - Wylie keyboard 3. in the search textbox, upper right of window, enter: phyogs bsgrigs What is the expected behavior? ཕྱོགས་བསྒྲིགས་ The above was entered in a separate program and the resulting Unicode string copy/pasted here What went wrong? ཕྱཨོགས་བསྒརིགས་ The above was entered directly into this textbox via the MacOS builtin Tibetan - Wylie keyboard. The Tibetan composed in this textbox is not the same as the expected, which is correct. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 61.0.3163.100 Channel: stable OS Version: OS X 10.12.6 Flash Version:
,
Nov 8 2017
,
Nov 8 2017
yoichio@ I'm not sure how to revert your patch to verify... Can you take a look if it's related to your change? Thanks! --- My bisect is pointing to: https://chromium.googlesource.com/chromium/src/+log/cc1b6b6973d5f132656aac5f5e7def51ec187048..80478c4257e298248e380b62e941ab4c2f775b12 Suspecting: https://chromium.googlesource.com/chromium/src/+/80478c4257e298248e380b62e941ab4c2f775b12 Bisect Command: python tools/bisect-builds.py -a mac -g 377178 -b 377466 --use-local-cache -- --no-first-run --user-data-dir=/tmp https://cdn.rawgit.com/w3c/uievents/gh-pages/tools/key-event-viewer.html Repro Steps: 1. Focus the input box 2. Switch to Tibetan - Wylie keyboard 3. Press keys "phyo" Expected Resulting Character: "ཕྱོ" Actual Character: "ཕྱཨོ"
,
Nov 15 2017
"ཕྱོ": ཕྱོ "ཕྱཨོ": ཕྱཨོ Our guess is cursor is canonicalized while EditorCommand
,
Nov 15 2017
,
Nov 15
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 16
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by divya.pa...@techmahindra.com
, Nov 8 2017Components: -Blink Blink>Input
Labels: -Pri-2 M-64 Triaged-ET Pri-1
Owner: chongz@chromium.org
Status: Assigned (was: Unconfirmed)