W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2019

Re: [csswg-drafts] [css-ui] Spec the pointer-events property for non-SVG elements (#4438)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Thu, 07 Nov 2019 00:58:43 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-550570928-1573088322-sysbot+gh@w3.org>
The CSS Working Group just discussed `[css-ui] Spec the pointer-events property for non-SVG elements`, and agreed to the following:

* `RESOLVED: add pointer-events to css-ui level 4`

<details><summary>The full IRC log of that discussion</summary>
&lt;myles> Topic: [css-ui] Spec the pointer-events property for non-SVG elements<br>
&lt;myles> GitHub: https://github.com/w3c/csswg-drafts/issues/4438<br>
&lt;myles> AmeliaBR: The pointer-events property defines whether an element is clickable or not. If something has pointer-events: none, it's treated as transparent for clicks and you can click through it for whatever's underneath. It's not defined in any CSS spec. It's defined in SVG, which also has lots of extra values that relate to fill areas or stroke areas are clickable and other variations<br>
&lt;myles> AmeliaBR: The reason to discuss this is we got a bug report on SVG complaining that a particular behavior wasn't defined, and that behavior wasn't SVG-related. It was about CSS boxes and stuff that wasn't SVG related. So, what about writing up a spec for pointer-specs?<br>
&lt;myles> chris: SVG would be happy to see it turn up in another spec, so they can delete it from theirs<br>
&lt;myles> AmeliaBR: One thing that chris did discover when we were discussing it, there was a spec in CSS-ui that got pulled when trying to stabilize that spec because speccing out the actual details turned out to be complex. It seemed to have been pulled and never reappeared in a later draft. Speccing it won't be nice and easy because we have lots of legacy behavior<br>
&lt;myles> chris: This is widely implemented<br>
&lt;myles> AmeliaBR: We have lots of implementations of a property without a spec. But we should still do it, difficult or no<br>
&lt;heycam> +1 to moving pointer-events to css-ui<br>
&lt;myles> chris: This is valuable by itself to define what pointer event handling is for CSS<br>
&lt;myles> astearns: Since the editor of css-ui is not on the call, we can pile it on him<br>
&lt;myles> astearns: But, chris, you mentioned SVG would like to delete it ... you'd only be deleting a tiny part of it, because all of those other values would still be an add on for SVG<br>
&lt;myles> chris: They would until css-fill-n-stroke. So those parts would move there<br>
&lt;myles> astearns: I would expect that the current work that we are proposing for css-ui would only be the currently supported values.<br>
&lt;myles> AmeliaBR: That sounds like a good strategy. The SVG spec would continue to be a partial definition adding in the extra values.<br>
&lt;myles> chris: Yes. which is fine.<br>
&lt;myles> astearns: Anyone concerned about defining pointer-events in a CSS spec?<br>
&lt;myles> RESOLVED: add pointer-events to css-ui level 4<br>
&lt;myles> AmeliaBR: One final note: The first step is going to be putting together some tests to understand existing behavior and compatibility issues. If anyone wants to take the initiative to look at their implementation, that would be great<br>
&lt;myles> AmeliaBR: We only have parsing tests in WPT<br>
&lt;myles> astearns: Thanks everyone! Next week is a non-APAC time.<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4438#issuecomment-550570928 using your GitHub account
Received on Thursday, 7 November 2019 00:58:45 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:56 UTC