Re: [svgwg] vector-effect grammar should allow multiple effects (#725)

The SVG Working Group just discussed `vector-effect grammar should allow multiple effects`, and agreed to the following:

* `RESOLUTION: Change the grammar to allow multiple effects at once`

<details><summary>The full IRC log of that discussion</summary>
&lt;krit> topic: vector-effect grammar should allow multiple effects<br>
&lt;krit> GitHub: https://github.com/w3c/svgwg/issues/725<br>
&lt;krit> AmeliaBR: this came out of a review of tests.<br>
&lt;krit> AmeliaBR: mostly parsing tests. The tests matched the grammar in the spec but not the logical grammar.<br>
&lt;krit> AmeliaBR: ... you should be able to specify multiple of the effects<br>
&lt;krit> AmeliaBR: stakagi commented that this is how the polypill implemented it.<br>
&lt;krit> AmeliaBR: Though most browser implementations just support the keywords yet.<br>
&lt;krit> myles: there should be a set of properties that map to a certain behavior, not a list<br>
&lt;krit> AmeliaBR: they describe the effect but not the order of operation. We need to define the meaningful order.<br>
&lt;krit> myles: if all browsers are just implementing the one keyword are we waiting for implementations?<br>
&lt;krit> AmeliaBR: yes, at this point, the new content is at-risk<br>
&lt;krit> myles: polyfills count as implementation, do they?<br>
&lt;krit> AmeliaBR: yes<br>
&lt;krit> AmeliaBR: at this point it is about changing the grammar<br>
&lt;krit> myles: all the descriptions could be in conflict but maybe I am complicated here. We maybe should describe in more detail which transforms apply in which order. But am fine with changing the grammar, the issue at hand.<br>
&lt;krit> RESOLUTION: Change the grammar to allow multiple effects at once<br>
&lt;krit> s/Change the grammar/Change the grammar of vector-effect property/<br>
&lt;krit> krit: should the concerns from myles go into a different issue?<br>
&lt;krit> AmeliaBR: probably<br>
&lt;krit> AmeliaBR: we could leave the text as is for now and wait for implementer feedback. However, this could lead to different implementation behavior<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/725#issuecomment-525017974 using your GitHub account

Received on Monday, 26 August 2019 20:26:09 UTC