Re: [fxtf-drafts] [css-masking] Disabling masks and clipPaths when display is none (#245)

The SVG Working Group just discussed `Disabling masks and clipPaths when display is none`.

<details><summary>The full IRC log of that discussion</summary>
&lt;krit> topic: Disabling masks and clipPaths when display is none<br>
&lt;krit> GitHub: https://github.com/w3c/fxtf-drafts/issues/245<br>
&lt;krit> AmeliaBR: This one Is tricky since there is a case where the browser implementations do not match the spec.<br>
&lt;krit> AmeliaBR: We need to figure out what browsers are doing in the finer details.<br>
&lt;krit> https://github.com/w3c/fxtf-drafts/issues/245#issuecomment-390863839<br>
&lt;krit> krit: Did the investigation on browser support for &lt;clipPath> and &lt;mask><br>
&lt;krit> krit: also differed between resources applied to HTML or SVG elements<br>
&lt;krit> krit: seems like browsers are doing more or less the same with 2 exceptions (see comment https://github.com/w3c/fxtf-drafts/issues/245#issuecomment-390863839)<br>
&lt;krit> krit: The CSS WG discussed the issue and let it to the SVG WG to resolve on the final behaviour.<br>
&lt;krit> krit: IMO there are 2 possibilities: 1) Ignore the mask/clipPath, has no effect on rendering 2) keep it unspecified<br>
&lt;krit> chris: This was a change we made midway at the beginning of SVG. On SVG Filters we got no output. So we said if filters are broken it has no effect.<br>
&lt;krit> chris: So I expect that the implementations were different.<br>
&lt;krit> AmeliaBR: This is not about broken masks/clipPath. It is about display: none on resource itself.<br>
&lt;krit> chris: at the time &lt;defs> was described as do-not render<br>
&lt;krit> chris: this was not implemented as expected. It lead to implementations not rendering anything in &lt;defs> and might be the source of what we see today.<br>
&lt;krit> krit: Yes, that seems the case for some browsers that do not create a rendering tree for &lt;defs> content or elements with display none<br>
&lt;krit> AmeliaBR: Agree that we should follow what implementations do.<br>
&lt;krit> krit: So are members fine to say it should not apply to rendering the SVG/HTML element? Matching the majority of browsers but keep an option for others to implement it differently for technical reasons?<br>
&lt;krit> AmeliaBR: Not a fan of should instead of must but if it helps implementation to conform to the spec.<br>
&lt;krit> krit: I understand the concerns with the proposals but do I hear objections?<br>
&lt;krit> chris: no<br>
&lt;AmeliaBR> display: none and filters, https://github.com/w3c/csswg-drafts/issues/4213<br>
&lt;krit> AmeliaBR: we have a similar issue for filters. Should it work the same way?<br>
&lt;krit> AmeliaBR: FF seems to disable rendering of the element which seems less useful<br>
&lt;krit> krit: So similar results as for mask/clipPath<br>
&lt;krit> krit: Can we agree to let all behave the same?<br>
&lt;krit> AmeliaBR: yes.<br>
&lt;krit> AmeliaBR: as long as we have tests in place.<br>
&lt;krit> krit: I can definitely add tests to web platform tests<br>
&lt;krit> AmeliaBR: and we would need edits to the specs.<br>
&lt;krit> AmeliaBR: we have places where we say display does not apply and now we need to describe how it does have an affect. And we need to sync all the changes across all specs and SVG2<br>
&lt;krit> krit: fair point<br>
&lt;krit> proposed resolution: display: none on mask/clipPath/filter element should have no affect on the rendered SVG/HTML element the resource applies to as in it was not specified for that element<br>
&lt;AmeliaBR> proposed resolution: display: none on mask/clipPath/filter element (or ancestor) causes the graphical effect to be ignored, so there is no impact on the rendering of the SVG/HTML element the resource applies to (as if it was not specified for that element)<br>
&lt;krit> RSOLUTION: display: none on mask/clipPath/filter element (or ancestor) should causes the graphical effect to be ignored, so there is no impact on the rendering of the SVG/HTML element the resource applies to (as if it was not specified for that element)<br>
&lt;AmeliaBR> s/RSOLUTION/RESOLUTION/<br>
&lt;krit> trackbot, stop telcon<br>
&lt;trackbot> Sorry, krit, I don't understand 'trackbot, stop telcon'. Please refer to &lt;http://www.w3.org/2005/06/tracker/irc> for help.<br>
&lt;krit> 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/245#issuecomment-536750049 using your GitHub account

Received on Monday, 30 September 2019 20:59:31 UTC