W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2018

Re: [csswg-drafts] [css-ui] Control whether an element is findable/searchable (Ctrl+F) (#3460)

From: Brian Birtles via GitHub <sysbot+gh@w3.org>
Date: Wed, 19 Dec 2018 23:19:44 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-448784441-1545261583-sysbot+gh@w3.org>
>  3\. How do findability, selectability, copyability, etc. interact with similar annotation methods, such as ruby annotation or [interlinear glosses in linguistics](https://en.wikipedia.org/wiki/Interlinear_gloss)?

For the particular case of ruby, it seems like UAs have the information needed to ignore ruby text when doing find in page (or alternatively match only the ruby text and ignore the base text) so this would just be a quality of implementation issue? That obviously doesn't help with the other use cases you mentioned, however.

I'd be a little bit concerned with authors abusing this (e.g. publishers deliberately making their content not searchable) but presumably UAs would provide a way to override this just like one can <kbd>Shift</kbd>+right click an element to get the native context menu when the content is overriding it.

GitHub Notification of comment by birtles
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3460#issuecomment-448784441 using your GitHub account
Received on Wednesday, 19 December 2018 23:19:45 UTC

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