- From: Carlos Lopez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Sep 2022 16:57:41 +0000
- To: public-css-archive@w3.org
@Loirooriol I'm tracking the performance issues with Chrome here: https://bugs.chromium.org/p/chromium/issues/detail?id=1360404#c14 Which might help explain where I'm coming from. Chrome+NVDA also lets you navigate and activate inert checkboxes, but that's likely a Chrome implementation bug or NVDA bug. I am probably putting the cart before the horse a bit with my explainer. The problem is But I don't see any implementation of inert being reasonable from a performance viewpoint with all the tree-walking that is required for set `Disabled State`. Considering `showModal()` makes the entire `#document` inert, it's probably a guaranteed framedrop on most devices. Nothing in `inert` spec says inert needs to be he hidden from accessibility. But if implementers can treat inert the same as they treat `content-visibility`, (and not have to treewalk), then implementation can be more reasonable. Also, I'm actively tracking Chrome, but Firefox and Safari suffer from the same long processing requirement of the entire DOM tree. Saying both `content-visibility` and `inert` apply a common set of characteristics on trees may help alleviate implementation pain. I'm not entirely sure why `content-visibility` doesn't need to treewalk, whereas `inert` does. From *user interaction perspective*, they should both be skipped equally (hence the shared logic proposition). -- GitHub Notification of comment by clshortfuse Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7703#issuecomment-1239649852 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 16:57:43 UTC