- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Feb 2021 20:57:12 +0000
- To: public-css-archive@w3.org
> > why Find gets special treatment, given the other ways content is exposed by UAs > > Making find an unique exception is something I would argue is indeed wrong. In the ideal world, the provisional content would also display in the accessibility tree (even as a place-holder template). In a way, I think we want something that says "this is not visible to the user yet, but it should be searchable/scannable" (and the UA's find feature is only one way to do so). After that, user agents might have bugs, and initially limit this to only search if that is the only thing they have budget for, but I feel this would be wrong indeed. We've already resolved not to make find special and expose this feature through all appropriate algorithms. -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5595#issuecomment-776239302 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 February 2021 20:57:14 UTC