3 ms·
Ctrl-f is often overriden for a reason, though. On modern shitty React sites content outside the viewport may not be loaded into the DOM, so the browser find wo
by rjh29 3y ago
Ctrl-f is often overriden for a reason, though. On modern shitty React sites content outside the viewport may not be loaded into the DOM, so the browser find won't even work. It is quite frustrating the scroll past some text, ctrl-f for it and get "no results".
- shadowgovt 3y agoCorrect. The most common perpetrator of "stealing" ctrl-f I use is the Google drive suite (Sheets, Docs, &c) and it's basically necessary. That operation is executed server-side. The client doesn't have the data to do the search. But that should be an exception, not the rule.
- eddd-ddde 3y agoGoogle at least gets it right, I almost never used a generic site's search function cause they never help me find what I want
- Falkon1313 3y agoThat's just a broken site. Breaking it in a different way doesn't fix it.
- rjh29 3y agoSuch "broken" sites happen to include some of the most popular sites on the internet, so I don't think anyone cares.