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: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
Date: Mon, 04 Nov 2019 21:42:12 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-549560326-1572903731-sysbot+gh@w3.org>
Relevant background, unearthed by @svgeesus:
https://wiki.csswg.org/spec/css4-ui#pointer-events

> pointer-events
> Moved from CSS3-UI editor's draft because it was the top source of issues for the 2nd CSS3-UI LCWD, and because it requires documenting previously undocumented web platform hit-testing model.
> 
> Incorporate spec text from:
> 
> pointer-events spec text
> Consider just specifying pointer-events:none, and reserving the other keywords as undefined in CSS (at this level of spec.
> 
> input from zewt, wilto asking for pointer-events:none in particular (#whatwg 2012-227)
> Consider use-cases, in particular for pointer-events:none;
> 
> make sure things that use CSS opacity:0 transitions aren't clickable when they're hidden. (zewt on #whatwg 2012-227)
> disable clicks on elements that are transitioning on/off screens (zewt on #whatwg 2012-227)
> prevent transparent elements that overlap clickable ones from getting in the way (zewt on #whatwg 2012-227)
> Consider adding a 'paint-order' value, as per Tokyo 2013 discussion
> 
> this would replace the normal DOM-order user-event bubbling with bubbling through the result of elementsFromPoint()
> could be used with positioned elements displayed outside their DOM parent
> could be used in fragmented content to include the fragment container

-- 
GitHub Notification of comment by AmeliaBR
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4438#issuecomment-549560326 using your GitHub account
Received on Monday, 4 November 2019 21:42:14 UTC

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