Press-and-hold character input still broken in Chrome 50
Reported by
p.stephani2@gmail.com,
Apr 25 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36 Steps to reproduce the problem: This issue is somewhat similar to https://bugs.chromium.org/p/chromium/issues/detail?id=460999 and https://bugs.chromium.org/p/chromium/issues/detail?id=94630. Some variants of the problem (e.g. using digits or arrow keys) have been fixed in Chrome 50, but the issue described below still exists. 1. Make sure "press and hold" is enabled (see e.g. https://discussions.apple.com/thread/7306504?tstart=0) 2. Set the keyboard focus to any HTML text input form (<input type=text>, <textarea>, etc.) 3. Long-press the "a" key until the character selection dialog appears 4. Press "1" to select "à", and immediately afterwards (with no more than ~100 ms delay) hit "a" again What is the expected behavior? "àa" is inserted What went wrong? "aàa" is inserted. Note the extra "a". This does not happen if the delay in step 4 is too long (> 100 ms). Did this work before? No Chrome version: 50.0.2661.86 Channel: stable OS Version: OS X 10.11.4 Flash Version: Shockwave Flash 21.0 r0
,
May 24 2016
,
Jul 13 2016
,
Jul 13 2017
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. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 21 2017
[mac triage] I can't repro this in a MacViews textfield, so it's something weird happening at the content/blink layer.
,
Jul 23
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
,
Jul 23
Still happens for me with Chrome 67.0.3396.99.
,
Jul 23
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by shrike@chromium.org
, Apr 28 2016Status: Untriaged (was: Unconfirmed)