Re: [csswg-drafts] [filter-effects] feComposite (Porter-Duff) operator values do not match those defined in the referenced [compositing-1] spec (#5267)

That's a fair summary :slightly_smiling_face: 

> this is definitely specified: "with in representing the source" is in the paragraph defining the "operator" attribute

I think there is a misunderstanding : `with in representing the source and in2 representing the destination` is fine to understand which is which for the two *attributes* of the filter, which correspond to the two *operands* of the porter-duff operation. 

However, the fact that the *operation* done on those two operands is `source-over` for the `over` *type* of the `operator` *attribute* is afaict somehow implicit ? I **do agree** it's more logical to see **`in over in2`** rather than **`in2 over in`** (at least this terminology is not ambiguous), but I don't see how it's implied by the sentence "in is the source, in2 is the destination", as this terminology used in [filters-effects] refers to [compositing-1] where it's always handled while explicitly separating the two cases (afaict).

> Personally, the "destination-NNN" operations still seems unnecessary to me. I presume you're not suggesting adding "source-in" as a synonym for "in"? I can see that source-in is not supported in Inkscape. So the argument that it should match exactly the list from css-compositing-1 seems to fall straight away. 

Honestly I don't really mind what is decided (and I'm clearly not in favor of having Inkscape behavior stay as is), I just want to fix Inkscape code in a conformant and logical way : my suggestion (driven by the sentiment that SVG and CSS/2dcanvas should strive to have identical arguments for identical operations) was to deprecate `over` in favor of `source-over` and add `destination-over`, but I'm personally fine with being sure that `over` means **`in over in2`** and not the other way around :) 

-- 
GitHub Notification of comment by mclegrand
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5267#issuecomment-655612821 using your GitHub account

Received on Wednesday, 8 July 2020 16:07:28 UTC