createPattern not working correctly with no-repeat

NEW
Unassigned

Status

()

Core
Canvas: 2D
P3
normal
2 years ago
2 months ago

People

(Reporter: driva95, Unassigned)

Tracking

({parity-edge, parity-ie, parity-safari})

48 Branch
x86_64
Linux
parity-edge, parity-ie, parity-safari
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [gfx-noted])

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
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
(Reporter)

Updated

2 years ago
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
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
Whiteboard: [parity-safari][parity-edge][parity-ie]

Updated

2 years ago
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.
maybe a dupe of bug 1263776.
See Also: → bug 1263776
Whiteboard: [parity-safari][parity-edge][parity-ie] → [parity-safari][parity-edge][parity-ie][gfx-noted]

Updated

2 years ago
See Also: → bug 1306956
(Reporter)

Comment 4

2 years ago
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?
Priority: -- → P3

Comment 5

8 months ago
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.