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: Joey Arhar via GitHub <sysbot+gh@w3.org>
Date: Wed, 11 Nov 2020 16:43:25 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-725530755-1605113004-sysbot+gh@w3.org>
In the last meeting, it sounded like there was concern over beforematch/hidden-matchable being available to other algorithms. I'd be happy to add support (fire beforematch) for these cases which I understand:
- Element fragments on navigation (can't make `window.location.hash` changes from script have async scrolling)
- `window.find` since we can try making the scrolling async since it isn't specced and has very low usage

> I’m suggesting this new API proposal could (should) allow that. The web app does not need to know if the agent initiating the search is the UA, or if it’s an AT behind it. How the UA exposes that search API to the AT is an implementation detail.

I agree, and I would be happy to say that the user agent should feel free to fire beforematch under hidden-matchable during behavior similar enough to the user intent in find-in-page.

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 November 2020 16:43:26 UTC

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