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, 18 Nov 2020 22:20:16 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-729993536-1605738015-sysbot+gh@w3.org>
Thanks for the discussion!

> My plan is to have a quick discussion (10 min?) at the beginning of the next meeting focused on a yes/no answer to the “Is this worth pursuing” question. So please bring up any latent deal-breakers here.

From what I could hear, there was no objection about exposing hidden content, it was just about which algorithms, accessibility, and other details. If anyone has an issue with the approach in general, please say so, otherwise we’ll just focus on the details.

If possible I’d like to discuss point 2 from [this comment](https://github.com/w3c/csswg-drafts/issues/5595#issuecomment-722006919), which is whether it’s the right idea to integrate this feature with content-visibility, as the first agenda item next time.

> Does the difference in show/hide behavior for various ways of scrolling to content have to be solved for this to be viable?

The consistency argument in favor of firing beforematch for element fragments is pretty strong. I agree we should plan on firing beforematch for these fragments. Let’s continue this discussion of how to do so in the parallel html issue: https://github.com/whatwg/html/issues/6040

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 November 2020 22:20:18 UTC

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