Re: [csswg-drafts] [css-ui] Should inertness be exposed as CSS property? (#7021)

The CSS Working Group just discussed `[css-ui] Should inertness be exposed as CSS property?`, and agreed to the following:

* `RESOLVED: Will not add an inertness property for now.`

<details><summary>The full IRC log of that discussion</summary>
&lt;emeyer> Topic: [css-ui] Should inertness be exposed as CSS property?<br>
&lt;emeyer> Github: https://github.com/w3c/csswg-drafts/issues/7021<br>
&lt;JakeA> My slides were all from https://www.youtube.com/watch?v=8FuafvJLDpM<br>
&lt;emeyer> oriol: This is something that appeared in discussions about inertness.  The main thing of inertness is it sets events.<br>
&lt;emeyer> …Proposing that inertness shoudl be exposed as a CSS property.  It could be like the ‘hidden’ attribute to ‘display: none’.<br>
&lt;emeyer> …Argument in favor is that inert sets certain kinds of styling.  This would allow authors to use selectors to make elements inert.<br>
&lt;emeyer> …Atrgument against is that implementations are tracking inertness by way of unexposed inherted properties.  If we expose it, then we should probably change this to be non-inherited that propogates by means other than inheritance.<br>
&lt;emeyer> …I don’t have a strong opinion, but would like a resolution one way or the other.<br>
&lt;Rossen_> q?<br>
&lt;emilio> q+<br>
&lt;emeyer> …emilio and annevk expressed oppoition.<br>
&lt;emeyer> emilio: I think this can be added if we want, but given that once an element is inert, it can’t be not-inert, the usefulness of the property seems limited.<br>
&lt;emeyer> …I also don’t like the idea of making a thing propogate outside of inheritance.<br>
&lt;emeyer> s/oppoition/opposition/<br>
&lt;emeyer> Rossen: Does anyone object to waiting until better use cases or louder voices appear?<br>
&lt;emeyer> RESOLVED: Will not add an inertness property for now.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7021#issuecomment-1041931621 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 16 February 2022 17:51:09 UTC