Able to reproduce the issue on Mac Retina 10.12.5 using chrome latest Canary-61.0.3159.0 as per the above html file.
Manual bisect info:
-------------------
Good-61.0.3151.4-Revision-484781
Bad-61.0.3152.0-Revision-485105
Per revision bisect info:
------------------------
You are probably looking for a change made after 485039 (known good), but no later than 485040 (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/5e67601472f51e96298b2b4edfa7286470bf8865..06adb5e74eb341b5a1fa68fed4e489f6f62ec5e8
Possible suspect:
-----------------
https://chromium.googlesource.com/chromium/src/+/06adb5e74eb341b5a1fa68fed4e489f6f62ec5e8
sunxd@Could you please take a look and reassign to the right owner if it is not related to your change.
Note:
No issue observed on Windows 7,ubuntu 14.04 & Mac book air.
Thanks..!!
This bug reproduces if we composite border radius, even if mask tiling is disabled. Hi enne@ and trchen@, can you provide some insights on this?
Also if I change the border to 1.5px, the text is rendered clearly.
Another report came in of this broken on 61.0.3163.79. Does not appear to repro on 62.0.3202.9.
Bisecting now.
Reading comment 8 now, I see that this bug was actually not fixed by the revert. And now it
made it into 61 stable. OTOH, comment 8 seems to indicate that the bug already exists in Chrome
60 and even earlier, since border-radius masking for non-stacking-context cases has been
launched for a while.
Comment 1 by jmukthavaram@chromium.org
, Jul 18 2017Labels: -Type-Bug -Needs-Bisect hasbisect-per-revision Type-Bug-Regression
Owner: sunxd@chromium.org
Status: Assigned (was: Unconfirmed)