- From: Carlos Lopez via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Sep 2022 12:44:38 +0000
- To: public-css-archive@w3.org
I apologized. I misunderstood the `Disabled State` to the same as a form control disabled state, which it is not. It is an interactivity state. That means that there is no real required treewalking to change the style or layout (eg: `:disabled`) and implementers should probably address performance concerns based their own code structure. That means this is would be strictly a language clarity change, not functionality change. Still, saying `content-visiblity:hidden` is inherently inert in spec could allow them to share logic without concerns of falling out of spec. -- GitHub Notification of comment by clshortfuse Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7703#issuecomment-1240668086 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 September 2022 12:44:40 UTC