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

I would expect that an invalid `kernelMatrix` value would be treated equivalently to no `kernelMatrix` attribute at all.

This was effectively how it worked with `<feColorMatrix>`, even if it wasn't not explicitly specified.  The fact that this causes the primitive to becomes a no-op or "pass-through" effect is a consequence of those initial values.  However, `<feConvolveMatrix>` didn't have clearly defined default values to start out with.

I'm certainly happy to define it such that invalid values result in a no-op primitive, but I'd like to be clear that a missing `kernelMatrix` attribute has the same effect as an invalid one.  The edits in seem to me to be working around the issue without clearly defining an initial value for `kernelMatrix`.

GitHub Notification of comment by AmeliaBR
Please view or discuss this issue at using your GitHub account

Received on Monday, 1 January 2018 00:24:54 UTC