first-letter CSS selector break multi-character utf8 symbol
Reported by
ludovic....@sculpteo.com,
Sep 1 2017
|
||||||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36
Steps to reproduce the problem:
1. Add a multi-character utf8 symbol at start of an element p.broken
2. Apply css rule p.broken:first-letter { color: green; font-size: 5em; }
3. Notice how stuff is broken
What is the expected behavior?
If the utf8 symbol is an emoji cat, I expect to see a big green emoji cat followed by normal text
What went wrong?
Emoji cat got cut in two. Instead of big green cat, I can see two invalid utf8 caracter symbol. First one being big and green, second is not.
Did this work before? N/A
Does this work in other browsers? N/A
Chrome version: 57.0.2987.98 Channel: n/a
OS Version: debian 5.9
Flash Version:
I only tested in firefox beside chromium and it doesn't split the utf8 symbol.
,
Sep 4 2017
Able to reproduce the issue on M60 #60.0.3112.113 on windows 7 , Mac os and ubuntu 14.04 . Issue got fixed in M62 and providing the reverse bisect results below, Good build: 62.0.3188.0 (Revision: 495023). Bad build: 62.0.3186.0 (Revision: 494273). You are probably looking for a change made after 494920 (known good), but no later than 494921 (first known bad). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/0d92bb0a3d9eb07dd53a9ae263bdedb7dad601e7..02d9bf5911935920465f10eac7b62b718851b401 From the CL above, assigning the issue to the concern owner @Xiaocheng Hu - Could you please merge the fix to M61/M60. Thanks!
,
Sep 4 2017
Requesting merging revision 02d9bf5911935920465f10eac7b62b718851b401 to M61 as of #2.
,
Sep 4 2017
This bug requires manual review: We are only 0 days from stable. Please contact the milestone owner if you have questions. Owners: amineer@(Android), cmasso@(iOS), ketakid@(ChromeOS), govind@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 5 2017
This bug was originally reported on M57, exists on M60 as well (not M61 regression) and we already cut M61 Stable RC. Hence, I'm rejecting merge to M61. Please let me know if there is any concern here. Thank you.
,
Sep 5 2017
This seems fine, according to the bisect in issue 723848 this is a non-regression issue. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by shend@chromium.org
, Sep 4 2017Status: Untriaged (was: Unconfirmed)