Issue metadata
Sign in to add a comment
|
Unwanted character in new tab's address bar
Reported by
vitaly.c...@gmail.com,
Apr 10 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/57.0.2987.98 Chrome/57.0.2987.98 Safari/537.36 Steps to reproduce the problem: 1. Switch keybord layout to russian (probably, any non-english) 2. Click somewhere on web page (focus should NOT be in address bar) 3. Press Ctrl+T to open new tab What is the expected behavior? New tab should open, and focus should be in _empty_ address bar What went wrong? New tab opens, but in address bar there is already letter е (in russian). Which is placed on the same keyboard key as t. Did this work before? Yes 54 or 55 Chrome version: 57.0.2987.98 Channel: stable OS Version: Ubuntu 16.04 Flash Version: Shockwave Flash 11.2 r999 Incorrect behavior only on russian layout (probably, any non-english) and only if focus before pressing Ctrl+T is not on address bar. I've noticed it in Chromium 56, and 57 also has this bug.
,
Apr 10 2017
Hello! I've tested it with Colemak layout, and it seems ok, as well as with Polish. But I've also tested with Ukrainian, Bulgarian and Thai layouts and with all of them there is bug. 'е' in Russian and Ukrainian, 'ш' in Bulgarian, and 'ะ' in Thai appears in address bar. So it seems like the problem is on layouts where symbol on key, which is on hotkey for new tab, is non-latinic. So maybe it is connected with charset or something. Could you please try on one of that problem layouts? Also i've noticed that problem is relevant for on screen keyboard too. So maybe i can record video, if it is needed. I have this problem on two machines, desktop with Ubuntu 16.04 and laptop with Ubuntu 16.10. On both it is Chromium 57 64-bit. Thank you.
,
Apr 11 2017
This issue looks similar to bug 673302 , Hence merging in to it. Feel free to undupe if it's a different issue. Thanks!
,
Apr 11 2017
Upduping the same as the issue still exist in latest M57 build i.e 57.0.2987.133. Able to reproduce the issue on Ubuntu 14.04 using latest chrome stable #57.0.2987.133 but the same is not reproducible in the latest dev #59.0.3063.4 and latest beta #58.0.3029.54. Reverse Bisect Information: ===================== Good build: 58.0.3013.0 Revision(431463) Bad Build : 58.0.3012.0 Revision(431726) Change Log URL: https://chromium.googlesource.com/chromium/src/+log/58084dd8f1d79ce115ee976daa4f1d6b8d51481b..4127317ca378c1cd8be4dd09428f0dd232888f68 From the above change log possible CL that fixed this issue: Review-Url: https://codereview.chromium.org/2580483002 chongz@ - Could you please check and merge the fix to M57 if it is a valid candidate. Adding label ReleaseBlock-Stable as it seems to be a recent regression. Thanks...!!
,
Apr 11 2017
,
Apr 11 2017
@krajshree IIUC M57 is already in stable and M58 is about to be released, do you think it's still worth the risk of merging it? Also I don't quite understand what does the label 'ReleaseBlock-Stable' mean?
,
Apr 13 2017
Thanks Rajshree for reverse bisecting. We do not have any planned releases M57 and the issue not reproducible in latest M58. We do not need to action here.Closing for now. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by b...@chromium.org
, Apr 10 2017