[
https://issues.apache.org/jira/browse/BATIK-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17440048#comment-17440048
]
Helder Miguel Alves Magalhães edited comment on BATIK-1317 at 11/7/21, 5:06 PM:
--------------------------------------------------------------------------------
No sure if it's a compliance bug: rendering in a recent Firefox version closely
resembles Batik behavior:
!Batik-1317-rendering_firefox.png!
Taking a look at the SVG source I'd say the "guilty" is
"mix-blend-mode:overlay" +style+ property, which means that the implementation
would have to implement +CSS 3+ (specifically [Compositing and Blending Level
1|https://drafts.fxtf.org/compositing-1/#mix-blend-mode]). Last time I checked,
Batik implemented [{*}CSS 2.1{*}, the normative version for SVG 1.1|#ref-CSS2].
The alternative proposal is rework the file to use SVG filter properties,
namely [feBlend|https://www.w3.org/TR/SVG11/filters.html#feBlendElement], which
should allow achieving the same visual result {+}using SVG alone{+}.
Dropping the "Important" flag and lowering the (apparently) excessive priority
given that a) there is now a reasonable workaround proposal and b) no rationale
has been provided for requesting such high priority. If you need to increase
again, please support you request with an explanation on the use case it's
blocking, number of affected users, etc..
I'd suggest labeling this as "Support for CSS 3 Compositing and Blending
module" and reworking to a "New Feature" request.
was (Author: helder):
No sure if it's a compliance bug: rendering in a recent Firefox version closely
resembles Batik behavior:
!Batik-1317-rendering_firefox.png!
Taking a look at the SVG source I'd say the "guilty" is
"mix-blend-mode:overlay" +style+ property, which means that the implementation
would have to implement +CSS 3+ (specifically [Compositing and Blending Level
1|https://drafts.fxtf.org/compositing-1/#mix-blend-mode]). Last time I checked,
Batik implemented [{*}CSS 2.1{*}, the normative version for SVG 1.1|#ref-CSS2].]
The alternative proposal is rework the file to use SVG filter properties,
namely [feBlend|https://www.w3.org/TR/SVG11/filters.html#feBlendElement], which
should allow achieving the same visual result {+}using SVG alone{+}.
Dropping the "Important" flag and lowering the (apparently) excessive priority
given that a) there is now a reasonable workaround proposal and b) no rationale
has been provided for requesting such high priority. If you need to increase
again, please support you request with an explanation on the use case it's
blocking, number of affected users, etc..
I'd suggest labeling this as "Support for CSS 3 Compositing and Blending
module" and reworking to a "New Feature" request.
> Bug in gradient rendering
> -------------------------
>
> Key: BATIK-1317
> URL: https://issues.apache.org/jira/browse/BATIK-1317
> Project: Batik
> Issue Type: Bug
> Components: GVT
> Affects Versions: 1.14
> Reporter: Konstantin Bulenkov
> Priority: Minor
> Attachments: Batik-1317-rendering_firefox.png, icon_256.svg,
> image-2021-10-29-15-39-54-461.png, image-2021-10-29-15-40-25-145.png
>
>
> When using Batik for SVG rendering in Swing, we faced a problem with
> gradients. See example below
> Expected (Rendered in Chrome):
> !image-2021-10-29-15-40-25-145.png!
> Actual:
> !image-2021-10-29-15-39-54-461.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-h...@xmlgraphics.apache.org
