Comment by glerk
5 hours ago
One trend that I can’t stand currently is the obsession with keyboard shortcuts everywhere even to the point of overriding browser defaults. Cmd+F focusing on the site’s search input instead of letting me search in the page with the browser’s search functionality (looking at you github and Linear).
I generally don’t need any fancy keyboard shortcuts on a website. I have a mouse, I can just click around.
What do you think about search override on some dysfunctional modern forums that can't display more than 3 replies, so if you used the built in browser search you wouldn't be able to find anything in a discussion?
But also, Vivaldi is awesome here is allowing you to block overrides for specific shortcuts so you Ctrl F is always yours
> dysfunctional modern forums that can't display more than 3 replies,
I assume that's overzealous virtualization/infinite scroll pagination? I don't have a solution, I think fundamentally we're building a workaround for a workaround and the root cause for the performance issues should be fixed. Somehow, HN is able to show a lot of comments per page and page loads are always O(100ms). I'm wondering what kind of sorcery they're using to achieve this.
But if you have to deal with this in your codebase, my instinct is still not to hijack the native Cmd+F, even if it only searches what's inside your viewport. You can expose some other command for full custom search (Cmd+K seems to be the standard, I think VSCode made that popular).
To the opposite, I'm a heavy user of keyboard shortcuts everywhere they exist. OTOH taking over the browser shortcuts, and especially the search, is something that I very much dislike.
I'm ok with them as long as they're not overriding what I have saved in my muscle memory (cmd+F for search, tab to change the focused element, cmd+L to go to the navbar, and a few others).
I think the user should be able to customize/disable those as much as possible if you do provide them.