- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Dec 2020 23:37:36 +0000
- To: public-css-archive@w3.org
In terms of preparing for the CSSWG meeting today, based on comments here and various offline discussions, I *think* we have consensus that the answer to both of the following questions is "yes": 1. Is it useful to have a way to specify that hidden content can be searched, and expose that to script? 2. Should the solution for item 1 apply to all methods of searching the UA provides, and all web-exposed APIs for searching? I hope we can resolve on the "yes" answers in the meeting. Then there is: 3. is having the content-visibility: hidden-matchable CSS value the right way to declare this feature in HTML content? Or is it better to have an HTML attribute, or an independent CSS property? Once we resolve on 1 and 2, I hope to gather feedback on 3 in the remainder of the 10 minutes. And as a quick reminder, there is some discussion of why we ended up proposing the hidden-matchable value at the top of this issue. (It doesn't cover an attribute alternative though.) -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5595#issuecomment-737561024 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 December 2020 23:37:38 UTC