-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transparent stroke/fill breaks SVG context #386
Comments
The following is the case with "explicit" Lines 212 to 214 in e08b5ca
For users who understand the inheritance in SVG, like us, this explanation may be sufficient. What I want to emphasize in this issue is that transparent colors implicitly change stroke-opacity /fill-opacity and opaque colors not.I think at least additional docs are needed. In particular, the latter |
The way I think Perhaps you could implement the rgba spec in Inkscape? |
Inkscape places importance on conforming to the standard, so I think it is difficult to implement it within SVG1. BTW, SVG 1.2 Full was canceled, so Line 342 in e08b5ca
I believe this problem can be mitigated by being able to determine whether |
At least since 2014, when I learned about Gadfly.jl, using transparent (i.e. alpha != 1.0) strokes and fills breaks the SVG context (i.e.
stroke-opacity
andfill-opacity
). Is this a known issue or desired behavior?Compose.jl/src/svg.jl
Lines 608 to 615 in e08b5ca
Compose.jl/src/svg.jl
Lines 617 to 624 in e08b5ca
Of course, adding
stroke-opacity="1"
/fill-opacity="1"
for opaque colors also causes context breaking.This problem can be avoided by specifying
stroke-opacity
andfill-opacity
manually.If it is an official solution, we need to fix the code of Gadfly. The
stroke(nothing)
setsstroke-opacity
to zero.While it is not a complete solution, at least, it is better to distinguish between the strokes/fills which actually exist but fully-transparent, and no-stroke/no-fill.
Compose.jl/src/property.jl
Line 54 in 2b561b0
Compose.jl/src/property.jl
Line 71 in 2b561b0
The text was updated successfully, but these errors were encountered: