- From: Rakina Zata Amni <notifications@github.com>
- Date: Wed, 21 Mar 2018 20:02:53 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 22 March 2018 03:03:16 UTC
> I'm a little worried the main use of this API will be for webpages to disable find-in-page. Is this work going to attempt to defend against that? The browser should allow the browser user to choose browser's find-in-page UI over the web page's own UI (the "power user" mechanism [discussed in the explainer](https://github.com/rakina/find-in-page-api#openfind-event)). Maybe we also need to give some kind of notification that the browser's find-in-page UI is being prevented so users know what's happening when no UI shows up? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/236#issuecomment-375163918
Received on Thursday, 22 March 2018 03:03:16 UTC