- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Sun, 21 Mar 2021 06:46:27 +0000
- To: public-css-archive@w3.org
So, if I understand correctly, if we could have something like a lazy accessibility tree, where you can compute things on demand rather than ahead of time, there would be no difference between accessibility and tabbing or search in page, but since we don't, there is a difference. Is that right? > As was mentioned in the meeting, this also potentially exposes a11y users via timing attacks. Or is the proposal to always style content-visibility: auto elements, regardless of a11y? That would be my proposal indeed, that said, I am not sure I understand the timing attack. Due to find in page (and tabbing), non-accessibility cases also sometimes need to compute the styles, so a delay caused by style computation would not necessarily be caused by usage of the accessibility tree, so it does not single out accessibility tree users. > Find-in-page is an explicit (uncommon) request by the user, it needs enough style to find the next match. Finding just the next one not enough, at least not to support the same behavior as currently. While it is true that the next match is highlighted in a particular way that is distinct from subsequent matches, and that even if you would normally highlight (in a different way) the rest, that doesn't matter because they are hidden anyway, you still need to find the rest: * All of Safari/Chrome/Firefox display the total number of matches * Chrome puts colored marks in the scollbar to indicate the places where find-in-page has found matches * If I understand correctly, when you use macOS's system-wide search (spotlight), it will find currently open pages (and maybe also history? I'm not sure) that contain the relevant terms, including if they are in a hidden-but-findable subtree, and that's powered by webkit indexing these things as it renders them, which means it needs to run styling on those parts as well. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5857#issuecomment-803522069 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 21 March 2021 06:46:28 UTC