- From: Joey Arhar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Jan 2021 21:57:42 +0000
- To: public-css-archive@w3.org
> One is content-visibility as I understand is optimization so UA doesn't hav e to build render tree. Issue with allowing finding inside is if UA on every page load tries to look for readerizable content it means every page load your hidden-matchable content will still need to be figured out enough to give right answer to indexing code. So you lose the optimization The same problem already exists with content-visibility:auto, which should also be searchable. I think this is more of an issue with content-visibility in general rather than content-visibility:hidden-matchable. > > Also how is content-visibility: hidden-matchable expected to interact with UA features like Reader view? If the content is important enough to allow Finding, should it be included in Reader views? > > Reader view sounds similar to Spotlight indexing. So I think hidden-matchable content could also be exposed to Reader. content-visibility:hidden-matchable should be considered a UA hint for features such as Reader mode, and leave it up to the UA to provide a performant implementation, just as it should for other features. -- GitHub Notification of comment by josepharhar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5595#issuecomment-754926916 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 January 2021 21:57:44 UTC