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

Issue 652096 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 602509
Owner:
Last visit > 30 days ago
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Compat



Sign in to add a comment

CANVAS patterns with no-repeat have pixel smudiging

Reported by andreabo...@gmail.com, Oct 2 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36

Example URL:
http://jsfiddle.net/emeagcnx/17/

Steps to reproduce the problem:
1. open the fiddle
2. look the code
3. watch the pattern painted on canvas

What is the expected behavior?
the pattern should be painted with no repeat, where asked, like safari does

What went wrong?
the pattern has pixel smoodging from sides.

Does it occur on multiple sites: No

Is it a problem with a plugin? No 

Did this work before? No 

Does this work in other browsers? No firefox

Chrome version: 53.0.2785.116  Channel: n/a
OS Version: OS X 10.11.5
Flash Version: Shockwave Flash 23.0 r0
 
Screen Shot 2016-10-02 at 10.22.00 AM.png
83.1 KB View Download
this fiddle illustrate better:
http://jsfiddle.net/emeagcnx/22/

Note that defect happens just with ctx.fill and ctx.fillText while fillRect works good.
I assume same problem happens with stroke. did not try yet.
Cc: kkaluri@chromium.org
Components: Blink>Canvas
Labels: M-55 OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on Windows-10, Ubuntu 14,04 and Mac OS 10.12 using chrome latest stable M53-53.0.2785.143 and earlier version of chrome M35-35.0.1849.0. Observed the canvas pattern has pixel smoodging from sides.

This is a non-regression issue and marking it as untriaged.

Comment 3 by junov@chromium.org, Oct 3 2016

Owner: xlai@chromium.org
Status: Assigned (was: Untriaged)
I believe this was fixed recently, or was it just another similar bug?

xlai?

Comment 4 by xlai@chromium.org, Oct 3 2016

Mergedinto: 602509
Status: Duplicate (was: Assigned)
This bug has already been fixed by https://codereview.chromium.org/2130063002 and its subsequent regression fixes. 

That fix (refs/heads/master@{#404491}) has not been rolled into chrome stable yet; that's why you can't see it if you just test on Chrome stable. But it's already in Chrome beta. I just double checked on Chrome latest Canary on a Mac machine and confirmed that this bug was fixed.
thanks for the informations!

Sign in to add a comment