Created attachment 8791179 [details] Screenshot from 2016-09-14 14-57-40.png User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.101 Safari/537.36 Steps to reproduce: I've written an app that use a canvas in which I'm moving an image with JS. When I use beginBitmapFill with repeat all works smootly, but if I use no-repeat it happens a small glitch. You can see the problem here: http://jsfiddle.net/4vp21mr7/1/ . I've attached an image that shows the bug. Sorry for my bad English but I'm not native
https://html.spec.whatwg.org/multipage/scripting.html#dom-context-2d-createpattern > 1. Create an infinite transparent black bitmap. > ... > 5. Replace any part of the image outside the area in which the pattern is to > be rendered with transparent black. it sounds like we shouldn't paint non-repeated area
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: beginBitmapFill not working correctly with no-repeat → createPattern not working correctly with no-repeat
fwiw, changing gfx.canvas.azure.backends to "cg" on OSX follows the spec.
Whiteboard: [parity-safari][parity-edge][parity-ie] → [parity-safari][parity-edge][parity-ie][gfx-noted]
Any news? I'm considering dropping FF support in my web app because it's going to be in production and there aren't news since one month ago. Anyone know if someone is working on it?
11 months ago
Priority: -- → P3
Hello! Will this bug be fixed or forgotten?
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-edge, parity-ie, parity-safari
Whiteboard: [parity-safari][parity-edge][parity-ie][gfx-noted] → [gfx-noted]
You need to log in before you can comment on or make changes to this bug.