New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 644354 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Arrow keys in <input> elements with "f" characters do not behave correctly with OpenSans font

Reported by jjen...@funmobility.com, Sep 6 2016

Issue description

Chrome Version       : 

Google Chrome	52.0.2743.116 (Official Build) m (64-bit)
Revision	9115ecad1cae66fd5fe52bd9120af643384fd6f3-refs/branch-heads/2743@{#728}
OS	Windows 
Blink	537.36 (@9115ecad1cae66fd5fe52bd9120af643384fd6f3)
JavaScript	V8 5.2.361.49
Flash	22.0.0.209
User Agent	Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
Command Line	"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --flag-switches-begin --enable-tab-audio-muting --flag-switches-end
Executable Path	C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Profile Path	C:\Users\jjensen\AppData\Local\Google\Chrome\User Data\Profile 4
Variations	b3888d8d-afba0f91
6345b824-3d47f4f4
7c1bc906-f55a7974
ba3f87da-ca7d8d80
f049a919-3f4a17df
f15c1c09-ca7d8d80
db19c37b-4ad60575
93731dca-3f4a17df
9e5c75f1-3e12a61c
f5dd6118-2f5721af
f79cb77b-3d47f4f4
b7786474-64e7d9a
73a8d7f1-ca7d8d80
868bda90-ca7d8d80
4ea303a6-ecbb250e
4117e878-f2d23ef0
7aa46da5-669a04e0
9736de91-ca7d8d80
dbffab5d-ca7d8d80
30e679f-3f4a17df
12a73824-3f4a17df
6844d8aa-669a04e0
f47ae82a-86f22ee5
3ac60855-486e2a9c
f296190c-4c073154
4442aae2-a90023b1
ed1d377-e1cc0f14
75f0f0a0-6bdfffe7
e2b18481-7158671e
e7e71889-4ad60575
9f0416c1-19dd9850
Compiler	MSVC 2015

URLs (if applicable) : https://jsfiddle.net/gbdsq4ex/3/
Other browsers tested:
  Firefox 48.0.2: OK
  Opera 39.0: FAIL
  Chrome 51.0.2704.103 on Mac OS X 10.11.5: FAIL
  Edge 13: OK
  IE 11: OK

What steps will reproduce the problem?
(1) Go to this URL: https://jsfiddle.net/gbdsq4ex/4/
(2) Place the cursor in the first text input.
(3) Use the right arrow key to move the cursor

What is the expected result?
The cursor should move one character to the right with each press of the arrow key

What happens instead?
The cursor skips every other press of the arrow key and moves two characters at a time.


This problem only seems to happen with the OpenSans font and only with the "f" character.  I used all other alphanumeric characters and could not reproduce the issue.  Using the Arial font does not reproduce the issue either.

 
Cc: kavvaru@chromium.org
Components: Blink
Labels: -Type-Bug -Pri-3 M-54 hasbisect OS-Linux OS-Mac OS-Windows Pri-2 Type-Bug-Regression
Owner: e...@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on windows 7, Linux Ubuntu 14.04 and Mac 10.11.6 using chrome version 53.0.2785.89 and canary 55.0.2853.0.
This is regression issue broken in M49.please find the bisect information as below

Narrow Bisect
==============
Good :: 49.0.2573.0  --   (official build revision 361233)
Bad:: 49.0.2574.0  --    (official build revision 361527)

CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/20f3b2d0ee459ed4d743ce9cd8c95417d74f6d04..fa7fc32c5940dfd3d734ed3231b1295da4c3303e

Possible suspect from the above CL
https://codereview.chromium.org/1474673003

eae@ Could you please look into this issue if it is related to your change,else please route this to an appropriate dev person.

Thanks,
Components: -Blink Blink>Fonts
I have confirmed the cause is https://codereview.chromium.org/1474673003. Reverting that change fixes the issue. So there must be a bug lurking in that feature.

Comment 3 by e...@chromium.org, Nov 1 2016

Status: WontFix (was: Assigned)
This is the correct (although sometimes surprising behavior)
The OpenSans font forms ligatures between adjacent f characters. The arrow keys move one *character* at the time, for the adjacent f characters two of them map to the same glyph and thus position. We cannot move glyph by glyph as that would disallow the underlying content to be changed.

Sign in to add a comment