W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > February 2018

Re: [fxtf-drafts] [filter-effects][css-masking] Should x, y, width, height on mask/filter elements map to SVG geometry properties?

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Mon, 26 Feb 2018 19:58:29 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-368630055-1519675108-sysbot+gh@w3.org>
The Working Group just discussed `Geometry attributes on <mask> and <filter>`.

<details><summary>The full IRC log of that discussion</summary>
&lt;AmeliaBR> Topic: Geometry attributes on &lt;mask> and &lt;filter><br>
&lt;AmeliaBR> Github: https://github.com/w3c/fxtf-drafts/issues/25<br>
&lt;AmeliaBR> Dirk: The mask, pattern and filter elements both take x,y,width,height attributes. These are regular attributes. But now we have geometry CSS properties for those attributes.<br>
&lt;AmeliaBR> ... So the question is, should these attributes now be presentation attributes attached to the CSS?<br>
&lt;AmeliaBR> ...My proposal is to defer this to a future spec. No change for now.<br>
&lt;AmeliaBR> Bogdan: Have you talked with the CSS WG, does this affect CSS masking?<br>
&lt;AmeliaBR> Dirk: It doesn't affect the application of the mask, it only affects the mask and filter elements.<br>
&lt;AmeliaBR> Amelia: My concern is authoring confusion. Once authors are used to the geometry properties, they would expect them to work on these elements. But I have no problem with deferring it for now.<br>
&lt;AmeliaBR> Bogdan: Generally speaking, making these properties could add a lot of complexity, because they we need to handle style matching for the elements before rendering.<br>
&lt;AmeliaBR> Dirk: As an implementer, I agree.<br>
&lt;AmeliaBR> ...But at this point, the main argument is that there are no implementations yet, so align the current spec with what is implemented &amp; defer to a next level.<br>
&lt;AmeliaBR> Bogdan: Is it worth opening a separate label, for things that are deferred beyond SVG 2?<br>
&lt;AmeliaBR> Amelia: Do we need it? These are already in separate, levelled CSS specs. Oh, except for pattern.<br>
&lt;AmeliaBR> Dirk: But even for pattern, any future work should probably be done in a separate SVG module.<br>
&lt;BogdanBrinza> resolution: Do not block CSS Masking/Filters on this and continue the discussion in SVG WG GitHub issue targeting SVG past 2.0<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/25#issuecomment-368630055 using your GitHub account
Received on Monday, 26 February 2018 19:58:33 UTC

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