W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2020

Re: [csswg-drafts] [css-contain-2] Proposal: content-visibility: hidden-matchable (#5595)

From: Alice via GitHub <sysbot+gh@w3.org>
Date: Sat, 07 Nov 2020 03:30:44 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-723383402-1604719843-sysbot+gh@w3.org>
> 1. Is “We” here the TAG? Googlers? Some other group?

Just me, talking with the folks working on this proposal.

> 2. Are any of those discussions linkable?

I think https://github.com/WICG/display-locking/issues/102 is the relevant public thread.

> Hypothetically, what if a general “find text” API were exposed in such a way that the AT could leverage the same path as the UA? VoiceOver already offloads some of its search functionality (next heading, next table, etc.) to WebKit. Perhaps a similar path could be used here.

This is why I noted "the way ATs work today" specifically. I agree, deeper integration into an AT's find-in-page mechanism would be ideal.

GitHub Notification of comment by alice
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5595#issuecomment-723383402 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 7 November 2020 03:30:45 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:22 UTC