News for hackers. Stuff that matters.
Re:A new spam policy for "back button hijacking" by raydev on Tuesday April 14, 2026 @02:51PM (#47769728)
If the page is lazy loading content then the local ctrl+f is not going to work, obviously.

If you’re hinting at an argument about whether lazy loading content should exist, that’s a separate discussion. In my experience, pages that override ctrl+f do it for a good reason

Re:A new spam policy for "back button hijacking" by xur17 on Tuesday April 14, 2026 @03:20PM (#47770141)
Even in those cases I'd prefer to just be able to natively search the content that has been lazy loaded. I've run into more than one website where the search functionality they bound to control-f is horrible.
Re:A new spam policy for "back button hijacking" by MrDOS on Tuesday April 14, 2026 @07:44PM (#47772920)
On Firefox, the “Prevent Shortcut Takeover” can be used to prevent websites from binding to Ctrl+F/Cmd+F: https://addons.mozilla.org/en-US/firefox/addon/prevent-short....
Re:A new spam policy for "back button hijacking" by johnfn on Tuesday April 14, 2026 @06:25PM (#47772265)
I think I've seen one page override ctrl-f for good reason -- it was a page that lazy loaded literally millions of lines of text that wouldn't have fit into RAM.

Every single other page that does it just wastes my time. It's always a super janky slow implementation that somehow additionally fails to actually search through all the text on the page.

Re:A new spam policy for "back button hijacking" by mghackerlady on Wednesday April 15, 2026 @02:18PM (#47783041)
then instead of lazy loading load chunks and paginate it like we used to