W3C home > Mailing lists > Public > public-svg-issues@w3.org > November 2018

Re: [svgwg] pointer-events auto

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Mon, 05 Nov 2018 21:51:20 +0000
To: public-svg-issues@w3.org
Message-ID: <issue_comment.created-436048757-1541454679-sysbot+gh@w3.org>
The SVG Working Group just discussed `pointer-events`, and agreed to the following:

* ``RESOLVED: Add `auto` as initial value for `pointer-events`, and define it to behave as `visiblePainted` ``

<details><summary>The full IRC log of that discussion</summary>
&lt;AmeliaBR> Topic: pointer-events<br>
&lt;AmeliaBR> github: https://github.com/w3c/svgwg/issues/574<br>
&lt;AmeliaBR> Eric: What's the history of this property? Browsers support `auto` but it's not in the spec.<br>
&lt;AmeliaBR> Amelia: I don't think SVG ever defined `auto`. But the property in general is under-spec'd. It's only defined for SVG, but it's supported for other elements in a way that isn't defined anywhere.<br>
&lt;AmeliaBR> Dirk: I think it used to be in CSS UI. Should probably be there again. But we still need to define what `auto` means for SVG elements.<br>
&lt;AmeliaBR> Eric: MDN is fairly clear that `auto` means `visiblePainted` for SVG elements. So the initial value doesn't change in practice.<br>
&lt;AmeliaBR> RESOLVED: Add `auto` as initial value for `pointer-events`, and define it to behave as `visiblePainted`<br>
&lt;AmeliaBR> Eric: I can make those edits.<br>
&lt;AmeliaBR> Amelia: We should also push the CSS WG to spec it separately, with definitions for non-SVG elements.<br>
&lt;AmeliaBR> Eric: I can follow up after I've made the edits.<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/svgwg/issues/574#issuecomment-436048757 using your GitHub account
Received on Monday, 5 November 2018 21:51:21 UTC

This archive was generated by hypermail 2.3.1 : Monday, 5 November 2018 21:51:22 UTC