Ugly looking selection and caret within text fields on particular fonts
Reported by
mer...@yandex-team.ru,
Jun 26 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 YaBrowser/17.6.0.1633 Yowser/2.5 Safari/537.36 Steps to reproduce the problem: 1. Type in a text with diacritic marks (like russian "Йцук" or german "Übersetzer") into the omnibox and select it 2. Open a Find bar (Ctrl+F), do the same 3. Open a google search webpage and do the same with the search input field 4. Select same word on the webpage And look at the vertical bounds of the selection, and of the caret beam, too. Try this with default Windows-7 system font "Segoe UI". Then change the "Message Text" font using the Control Panel. Change it for "Times New Roman". Relaunch the browser and try again. What is the expected behavior? 1) Selection must include all parts of glyphs, including diacritic signs. 2) It should be as symmetric as possible. What went wrong? Segoe UI is ugly: it has too high ascent value (extra 3px for 14pt font). This makes the selection of the edit field shift up (top space = 2px, bottom space = 5px in the omnibox; top space = 11px, bottom space = 13px in the find bar). On the other side, Times New Roman has smaller ascent. It looks OK in the omnibox, but cuts the breve sign of Й in the find bar. Arial also cuts the breve sign on the webpage input field. Did this work before? N/A Chrome version: 60.0.3108.0 Channel: dev OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 26.0 r0 Attached is a composite screenshot of selections. The left column is for default Segoe UI, the right one is for Times New Roman. Top row shows the omnibox. Second row shows the findbar. Third and fourth show the webpage. It uses same Arial and does not depend on system prefs.
,
Jun 26 2017
,
Jul 31 2017
Quickfixed here: https://chromium-review.googlesource.com/c/593615/
,
Dec 13 2017
,
Dec 13 2017
,
Dec 13 2017
For web content it is a bit more complicated as the selection height is limited by the row height. We could definitively do better though.
,
Dec 14
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
,
Dec 15
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by mer...@yandex-team.ru
, Jun 26 2017