W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > December 2017

Re: [fxtf-drafts] [filter-effects] Clarify what happens with failing pre-conditions on feConvolveMatrix

From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
Date: Sun, 31 Dec 2017 19:56:45 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-354621234-1514750203-sysbot+gh@w3.org>
I used this simple example to verify the behavior in implementations:

<svg width="100%" height="220" style="outline: 1px solid red" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
   <filter id="convolve">
      <feFlood flood-color="green" result="flood"/>
      <feConvolveMatrix kernelMatrix="1 0 0 0 1 0 0 0 -1 0" in="SourceGraphic" result="kernel"/>
      <feComposite operator="over" in="kernel" in2="flood"/>

 <g font-size="3em">
   <text x="225" y="75">Convolve</text>
   <text x="225" y="150" filter="url(#convolve)">Convolve</text>

* Firefox and Chrome treat the result of `feConvolveMatrix` as transparent black on failing preconditions.
* Safari does not render the entire element.
* Adobe Illustrator/PS makes the filter a pass through.

The pass through seems to be more in line to the behavior of browsers with failing preconditions on `feColorMatrix`'s `values` attribute. Here all browsers use the "initial value" instead which makes the filter a pass-through.

I couldn't verify Edge yet.

GitHub Notification of comment by dirkschulze
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/237#issuecomment-354621234 using your GitHub account
Received on Sunday, 31 December 2017 19:56:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:50:21 UTC