Re:A new spam policy for "back button hijacking"
by taco_emoji on Tuesday April 14, 2026 @11:03AM
(#47766575)
CTRL+F hijacking is necessary in some cases when apps are not displaying the full text that the user would expect to search. E.g. when there's a 10K-line code file and the UI is not loading the whole thing into DOM, but the user would expect a "find" to search that whole code file.
[ Parent
| on HN ]
Re:A new spam policy for "back button hijacking"
by rat_on_the_run on Tuesday April 14, 2026 @11:48AM
(#47767220)
They can have a search button for that, not hijacking default browser functions. Often I want both kinds of search.
Re:A new spam policy for "back button hijacking"
by pornel on Tuesday April 14, 2026 @11:47AM
(#47767205)
Browsers can deal with very long documents. Ctrl+F works like a breeze on HTML that's 100K lines long.
Browsers only struggle to run heavy JS frameworks that wrap every line in a dozens of spans with dozens of handlers and mutate it all on every line scrolled.