Open
Bug 1263776
Opened 9 years ago
Updated 3 years ago
createPattern with 'no-repeat' bleeds color from edges of pattern image
Categories
(Core :: Graphics: Canvas2D, defect, P3)
Core
Graphics: Canvas2D
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox48 | --- | affected |
People
(Reporter: yury, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: parity-chrome, parity-edge, Whiteboard: [gfx-noted])
Attachments
(2 files)
When fill() is used with pattern that was created with 'no-repeat' parameter, the 2d context paints the pattern once and the rest of the area is filled with color of the pixel from the pattern edge that is closest to the pixel that is being painted (a la GL_CLAMP_TO_EDGE). It is expected only image of the pattern is painted.
| Reporter | ||
Comment 1•9 years ago
|
||
Whiteboard: [gfx-noted]
Comment 2•9 years ago
|
||
Looking at the spec, it appears that no-repeat really does expect EXTEND_NONE behaviour, not clamping.
Our CanvasGeneralPattern::ForStyle() code uses ExtendMode::CLAMP for this case (since we don't support NONE in Moz2D).
CC'ing graphics people who might want to fix this :)
Updated•9 years ago
|
Comment 4•7 years ago
|
||
Would be cool if someone could fix this one day.
Any chance?
If is a cairo based render i could also give a shot.
Updated•7 years ago
|
Keywords: parity-chrome,
parity-edge
Comment 5•6 years ago
|
||
http://jsfiddle.net/emeagcnx/17/
This is an old javascript only reproducible case
Comment 6•6 years ago
|
||
Chrome uses the Decal tile mode now:
https://chromium.googlesource.com/chromium/src/+/89d63e3a995cf
And here's what Safari does https://github.com/WebKit/webkit/blob/10627ba484528fed3e7358b1801250bb004c8a99/Source/WebCore/platform/graphics/cg/PatternCG.cpp#L60
I wonder what Edge does.
Comment 7•6 years ago
|
||
Nodecanvas, a cairo based implementation of canvas under node uses a cairo native constant to define the no repat and does not bleed.
Comment 8•6 years ago
|
||
I wish an happy new year to all firefox devs here, but a special happy new year to the one that will eventually fix this bug.
Continue the great job!
Comment 10•5 years ago
|
||
Any chance someone will fix it?
Comment 11•4 years ago
|
||
Keywords: feature
Updated•3 years ago
|
Severity: normal → S3
Comment 12•3 years ago
|
||
Is it still being repaired?
You need to log in
before you can comment on or make changes to this bug.
Description
•