- From: Carlos Lopez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Sep 2022 19:18:43 +0000
- To: public-css-archive@w3.org
@Loirooriol Thanks. Maybe I'm not explaining it clearly. it's not a matter of making inert treated as `content-visiblity:hidden`. That makes no sense. It's the matter of making them the same base in terms abstraction: If all `content-visiblity:hidden` are implicitly inert, then an element can apply the same logic whether it is visible or inert. In psuedocode: * `ContentVisibilityHiddenElement implements InertElement`. Or a shared base type: * `ContentVisibilityHiddenElement implements NonInteractiveElement` * `InertElement implements NonInteractiveElement` But the rules in spec for `inert` do not match the rules for `content-visiblity:hidden`. Inert disables elements internally and has optional find-in-page whereas `content-visibilty:hidden` removes from accessibility tree and excludes find-in-page results. Diagrams:   -- GitHub Notification of comment by clshortfuse Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7703#issuecomment-1239780926 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 September 2022 19:18:45 UTC