I think one key thing that was missed in your review was the second paragraph of https://github.com/rakina/find-in-page-api/blob/master/README.md#openfind-event . Because of that, there shouldn't be any situation in which you're left with nothing, or "hijacked". In general, there's nothing in the spec that prevents the browser from displaying whatever UI it wants. The preventDefault() is just a signal that the page intends to supply its own UI, and so the browser might want to make the default API hidden behind a power-user mode (like holding down shift, or performing some gesture, or an icon in the URL bar...). Perhaps that could be made clearer? But in general I think it's understood that specs don't proscribe UI, and browsers are free to innovate. Some might hide it; some might show both; some might use machine learning to detect when the page-provided one is a good experience and dynamically swap them out... -- 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-380604773
Received on Wednesday, 11 April 2018 21:42:05 UTC