Firefox allows you to bypass right click hijacking by holding shift before pressing right click.
replyThere is also an option in about:config: "dom.event.contextmenu.enabled" set it to false
replyCTRL+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.
replyThey can have a search button for that, not hijacking default browser functions. Often I want both kinds of search.
replyBrowsers can deal with very long documents. Ctrl+F works like a breeze on HTML that's 100K lines long.
replyBrowsers 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.
Don't get me started on scroll hijacking.
replyGithub hijacks '/' and it's really annoying, it gets me all the time.
replySome also hijack the shortcuts to open devtools (like F12), so you have to find the option in the browser menu itself
replyYou can also click the address bar and then press you shortcut. Should be faster and works for all shortcuts AFAIK.
replyThank you!
replyThis misses the point. Websites are allowed to replace default keyboard shortcuts for a reason. There are only a few exceptions to this, like Ctrl+W. In other words, you can design your website however you want, except to make it more difficult to leave. This is an implementation of the same philosophy.
reply> you can design your website however you want, except to make it more difficult to leave.
replyWho decreed that page navigation is in scope and search navigation is outside?