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

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

From: Joey Arhar via GitHub <sysbot+gh@w3.org>
Date: Mon, 26 Oct 2020 15:17:47 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-716616377-1603725465-sysbot+gh@w3.org>
Thanks for the questions at TPAC!

I agree the details element is an important use case, it was brought up in this issue: https://github.com/WICG/display-locking/issues/162

- We could keep find-in-page synchronous for cases where we aren’t firing beforematch now that we are only going to fire it on hidden-matchable subtrees, but what is the benefit of keeping it synchronous? In stable chrome we are currently doing the full async code path for every find-in-page and there doesn’t seem to be any issues.
- For window.find, I don’t currently have plans to implement beforematch and such in it since it doesn’t really seem like there are important use cases for it and it has very low usage. The only reason I can think of is being able to test beforematch in WPT. Previously, I was more hesitant to change window.find since making it async could break the synchronous scrolling behavior of window.find. We could make the scrolling happen synchronously for non beforematch/hidden-matchable matches, but having both sync and non-sync behavior doesn’t sound amazing… what do you think?

You mentioned other use cases for beforematch than just find-in-page:
- ScrollToTextFragment is definitely a big use case we are supporting.
- Element fragments are more problematic since the page must scroll synchronously when the fragment is changed, which isn’t compatible with the async steps we have for the beforematch event which allows the page to reveal the content asynchronously. In addition, the page can already see the fragment on page load and observe changes with the hashchange event.
- What are the "addresses" and "metadata" use cases you talked about?

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 October 2020 15:17:52 UTC

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