Open
Bug 1351243
Opened 8 years ago
Updated 2 years ago
Consider whether context-stroke in SVG-as-an-image should use the initial value of 'none' from the context
Categories
(Core :: SVG, enhancement, P3)
Core
SVG
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox55 | --- | affected |
People
(Reporter: jwatt, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 obsolete file)
The reftests for bug 1058040 show a difference in behavior between fill and stroke when it comes to context paint for SVG-as-an-image. Specifically the tests context-fill-07.html and context-stroke-07.html.
These tests check what happens when the fill/stroke is not specified on the context but the SVG image uses the 'context-fill'/'context-stroke' values. The second <img> in the references checks what happens when a fallback color is specified, and the fill/stroke tests behave differently. In the fill test the color black is used instead of the fallback color. In the stroke case the fallback color is used.
The reason for this difference is that fill has the initial value 'black' (which we expose as the context-fill to the SVG image) but stroke has the initial value 'none' which we don't expose as we treat it as not providing a context color.
I'm not really happy with this difference.
Implementing bug 1350010 may impact on what we do here since then the exposed properties are explicit.
Updated•7 years ago
|
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Keywords: parity-chrome
Comment hidden (obsolete) |
Updated•2 years ago
|
Assignee: nobody → longsonr
Status: NEW → ASSIGNED
Comment hidden (obsolete) |
Updated•2 years ago
|
Status: ASSIGNED → NEW
Updated•2 years ago
|
Assignee: longsonr → nobody
Updated•2 years ago
|
Keywords: parity-chrome
You need to log in
before you can comment on or make changes to this bug.
Description
•