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

Re: [fxtf-drafts] [css-masking] Support <g> element is clipping paths

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Mon, 26 Feb 2018 20:21:16 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-368636826-1519676475-sysbot+gh@w3.org>
The Working Group just discussed `Support <g> element is clipping paths`.

<details><summary>The full IRC log of that discussion</summary>
&lt;AmeliaBR> Topic: Support &lt;g> element is clipping paths<br>
&lt;AmeliaBR> Github: https://github.com/w3c/fxtf-drafts/issues/17<br>
&lt;AmeliaBR> Amelia: I definitely support this as something I'd like to see in the future, but can be deferred for now.<br>
&lt;AmeliaBR> ... I don't think there is any real implementation reason for not allowing it, I think it was just a DTD convenience. Didn't want to allow &lt;g>, because then it would automatically allow anything that is allowed in &lt;g>.<br>
&lt;AmeliaBR> Dirk: There would still always be implementation complexities. I'm in favour of deferring to a future spec, if only because it's not implemented anywhere.<br>
&lt;AmeliaBR> Bogdan: Is that one of the suggestions you mention in the discussion, you've got some suggested edits there.<br>
&lt;AmeliaBR> Amelia: Looks like that's a slightly different issue, about indirect &lt;use> references. Edge supports them, other browsers don't.<br>
&lt;AmeliaBR> Dirk: At this point, I don't expect to get any implementation changes in time for this level of the spec.<br>
&lt;AmeliaBR> ... I think that's what the spec says.<br>
&lt;AmeliaBR> Amelia: I think the other issue is error handling. We don't know whether we really have cross-browser consistency in how they handle error states.<br>
&lt;AmeliaBR> Dirk: That should maybe be another issue.<br>
&lt;AmeliaBR> Bogdan: Even there, according to the notes in the issue, it looks like we have almost consistency, across 3 browsers.<br>
&lt;AmeliaBR> Amelia: Sounds like a good resolution, for all the details, is to run tests &amp; then try to make the spec match browser behavior.<br>
&lt;AmeliaBR> Dirk: Sounds good to me.<br>
&lt;BogdanBrinza> resolution: develop the tests to find the interoperable core of the error handling and match the specification to that<br>
&lt;AmeliaBR> Bogdan: If that's the last issue, let's wrap up early. Thank you very much for a productive call.<br>
&lt;AmeliaBR> trackbot, end telcon<br>
</details>


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

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