New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 610724 link

Starred by 1 user
Status: Fixed
Owner:
█ caryclark@chromium.org
Last visit > 30 days ago
Closed: May 2016
Cc:
█ kavvaru@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug-Regression



Sign in to add a comment

bezierCurveTo not clipped without 2d acceleratoin

Reported by axk...@gmail.com, May 10 2016 
Chrome Version       : Chromium	50.0.2661.94 (Developer Build) Built on 8.4, running on Debian 8.4 (64-bit)
URLs (if applicable) : https://jsfiddle.net/670pb0yL/2/
Other browsers tested:
  Google Chrome	50.0.2661.94 (Official Build) (64-bit)
 OK with 2d acceleration enabled, but same error if not.
  Iceweasel(firefox) 38.8.0 OK

What steps will reproduce the problem?
(1) Disable 2d acceleration (either due to hardware/libraries or flag)
(2) View the result

What is the expected result?
The square should be completely empty, meaning clipped out.

What happens instead?
The fill is actually clipped as expected, but the stroke isn't.

Please provide any additional information below. Attach a screenshot if
possible.
screenshot.png
115 KB View Download

Comment 1 by kavvaru@chromium.org, May 13 2016

Cc: kavvaru@chromium.org
Components: Internals>GPU>Canvas2D Blink
Labels: -Type-Bug M-52 hasbisect OS-Linux OS-Mac OS-Windows Type-Bug-Regression
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on windows 7, Linux Ubuntu 14.04 and Mac 10.11.4 using chrome version 50.0.2661.94 but is is fixed in version 52.0.2735.0.

Please find the reverse bisect information as below
Good::52.0.2735.0  --   (official build 393409)
Bad::52.0.2734.0  --   (official build 393126)

CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/536602c5d448afc7bd38524b450401c8a142a796..49ac8d40f0a2d24f85a7e5483045474e8d8eb617

Unable to find the exact suspect CL.Marking it as Untriaged to get it addressed.
Could any one please look into this issue if it requires merge or not.

Thanks,

Comment 2 by junov@chromium.org, May 13 2016

Components: -Blink -Internals>GPU>Canvas2D Blink>Canvas Internals>Skia
Owner: caryclark@chromium.org
Status: Assigned (was: Untriaged)
Did a finer bisect.
The fix was this CL: https://chromium.googlesource.com/skia.git/+/4cba202b7162fb5f364235dd29f0bdbd53a8e33c

Assigning to caryclark@ to consider whether the fix should be merged to M51

Comment 3 by caryclark@google.com, May 24 2016

Status: Fixed (was: Assigned)
Given that

- M52 is out
- this bug is not normally visible since 2D acceleration is enabled by default
- the bug was introduced in December without being noticed

I don't think it's worth the risk to roll back into M51.
►

Sign in to add a comment