Half of the time those sites also lazy load anyway so whatever you're looking for isn't even in the DOM yet

And lazy unload, so you can't find it even if you've already scrolled through the whole thing.

I used to hear it called "virtual scroll", and I remember webpages ballooning in RAM when they didn't do it.

the text content of the site is not what is ballooning the RAM.

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

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.

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....

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.

then instead of lazy loading load chunks and paginate it like we used to

Just use Ctrl+G - it does almost the exact same thing as Ctrl+F

it's asking me for a line number

Yeah, super annoying when that happens. A workaround is to click the address bar (or press ctrl+l unless that's been hijacked too) and then do ctrl+f.

Ctrl-f for page search and ctrl-k for website search[1].

[1] https://fmhy.net

Agreed. I also like slash / to focus the primary input like on youtube