Insufficient auto-height for <select> element when styled with mixed language fonts
Reported by
fatfat...@gmail.com,
Sep 14 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Steps to reproduce the problem: Create a <select> element in which the selected option has mixed language fonts. Example: https://jsfiddle.net/hj945u7b/ Fonts used: "Mplus 1p" from Google Fonts Early Access <link href="//fonts.googleapis.com/earlyaccess/mplus1p.css" rel="stylesheet" /> <select style="font-family: Arial, 'Mplus 1p';"> <option>abcdefghij すると、夜空に最初の流れ星が現れた。</option> </select> What is the expected behavior? What went wrong? Bottom part of the English alphabets are cut off. Did this work before? N/A Chrome version: 60.0.3112.113 Channel: stable OS Version: 10.0 Flash Version: Note that the issue only occurs on some of the fonts (e.g. "Meiryo", "Yu Gothic", which are Microsoft fonts).
,
Sep 15 2017
Tested the issue on 60.0.3112.113 , latest stable 61.0.3163.79 and latest canary 63.0.3216.0 using Ubuntu 14.04,Windows 10 and is reproducible by navigating to given jsfiddle. NOTE:In Mac 10.12.1 text is seen attached with dropdown border. Manual Bisect Info: =============== Good Build: 53.0.2781.0 Bad Build: 53.0.2782.0 You are probably looking for a change made after 402201 (known good), but no later than 402212 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/1a028fbffb2a321037ff2213b03418447998756d..4a06ab9ea2f882871c2f9d678513a1ce990ec8d4 Suspecting c2a23354aee0beef71541680def441d025dc37b9 from above changelog @glebl: Could you please confirm the behaviour and help in assigning to appropriate owner if this has nothing to done with you.
,
Sep 28 2017
Gleb is no longer working on Blink. Not really a regression. Gleb tried to fix this issue but had to revert the change as it broke a bunch of sites.
,
Sep 28
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
,
Sep 30
We're realistically not going to be able to fix this anytime soon, last time we tried it broke a lot of content. Closing. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nyerramilli@chromium.org
, Sep 14 2017