Canvas2DRenderingContext sometimes fills instead of stroke
Reported by
alexande...@gmail.com,
Oct 12
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Open attached html test case What is the expected behavior? Three line segments are drawn. What went wrong? A triangle is filled in bewteen two of the segments. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 69.0.3497.100 Channel: stable OS Version: OS X 10.13.6 Flash Version:
,
Oct 14
,
Oct 15
Thanks for filing the issue! Able to reproduce the issue on reported chrome version 69.0.3497.100 using Mac 10.13.1, same issue isn't seen on 60.0.3112.0, hence considering it as Regression and marking it as Untriaged. Adding Needs-Bisect label, will update the bisect info soon.
,
Oct 15
Thanks for the report.
,
Oct 15
,
Oct 16
++Able to reproduce the issue on reported chrome version 69.0.3497.100 and the issue isn't seen on latest canary 72.0.3581.3 using Windows 10, Mac 10.13.1 and Ubuntu 14.04 Bisect Information: ------------------- Last Bad Build: 71.0.3562.0 First Good Build:71.0.3563.0 Providing the chromium bisect as we are getting an error while doing per revision bisect. You are probably looking for a change made after 594604 (known good), but no later than 594617 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/65d577fb9759e31673e19d76db8b4a4e447dab39..cd031b000616f1d080e646a6fd545c03d94a369c https://skia.googlesource.com/skia.git/+log/5ea41fc89b26..88e4a9395a45 Suspecting: https://skia.googlesource.com/skia.git/+/cfe1264d7465b0791073969ba6375dcca20afec9 Review URL: https://skia-review.googlesource.com/157220 @Stephen White: Please help in assigning it to the right owner, if this isn't related to your change. Adding RBS for M-70, please feel free to adjust the milestone.
,
Oct 16
Yes, that change does seem to fix this problem.
,
Oct 16
[Auto-generated comment by a script] We noticed that this issue is targeted for M-70; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-70 label, otherwise remove Merge-TBD label. Thanks.
,
Oct 16
I suggest waiting for M-71.
,
Oct 16
Seems like no merge is needed to M71 per comment #6. Pls renove "Merge-TBD" label or request a merge to M71 if needed. Thank you.
,
Oct 17
,
Oct 18
Running a bisect-builds.py on a linux64 machine: You are probably looking for a change made after 568151 (known good), but no later than 568157 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/cafe788e00b3c748706f30b14c29cafbe44a55dc..b90af89c22a2a105152fcd9985b795c84c3ccd37
,
Oct 18
The first bad commit: https://chromium-review.googlesource.com/c/chromium/src/+/1099564
,
Oct 18
Yeah, this is probably a dupe of 884166 or 887103. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 Deleted