Position and animation change a text rendering
Reported by
sergen....@gmail.com,
Mar 24 2017
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3050.0 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Add element with animation of opacity or transform. 2. Add two elements with text inside. 3. Set position: relative for one of the boxes. What is the expected behavior? Text in both boxes looks the same. What went wrong? Text in box with position: relative renders by different algorithm. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 59.0.3050.0 Channel: canary OS Version: 10.0 Flash Version: Shockwave Flash 25.0 r0
,
Mar 27 2017
,
Mar 27 2017
Able to reproduce the issue on the latest canary(59.0.3051.3) and the latest stable(57.0.2987.110) on Windows-10, Mac OS 10.12.3 and Linux Ubuntu 14.04. Regressed in M-58: ================== Last good build: 43.0.2336.0 First bad build: 43.0.2337.0 Changelog: ========== https://chromium.googlesource.com/chromium/src/+log/ee11c06cea48829c79878a51b2afb875c943d48b..71e08c4d22fb6035bf80b8a110ede3e3d840861b Blink changelog: ================ https://chromium.googlesource.com/chromium/blink/+log/1da9649..e1c445e alancutter@: Could this be related to the https://codereview.chromium.org/1004623010 from the Blink CL. Note: Unable to provide the hasbisect per revision as the range is out of the supported range by the script.
,
Mar 28 2017
That CL enables unprefixed animation properties to be used. What happened is the animation stopped running for that page since it only uses unprefixed properties. Use the attached modified test case for the bisect instead, I've made it use the prefixed properties instead. (Given that this went as far back as 43 I wouldn't consider this a regression anyway).
,
Mar 28 2017
,
Mar 28 2017
As per the attached index.html file, this is Non-regression issue as seeing the same behavior on older chrome version: 30.0.1549.0/35.0.1849.0/40.0.2172.0 as well. Tested on Windows-10. Therefore, removing the Needs-Bisect label.
,
Mar 30 2017
,
Apr 2 2018
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
,
Apr 2 2018
This behavior is due to changes in text rendering when text gets a new composited layer. We cannot use sub-pixel text rendering in such cases because we are not sure of the background opacity. There are other open issues to enable sub-pixel in more cases, so closing this issue. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by tkent@chromium.org
, Mar 26 2017