We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Thread ini telah ditutup dan diarkib. Sila tanya soalan baru jika anda perlu bantuan.

Why such a massive hotkey redundancy?

  • 3 balasan
  • 1 ada masalah ini
  • 1 paparan
  • Balasan terakhir oleh cor-el

more options

locking as a duplicate of https://support.mozilla.org/en-US/questions/1073264 - please continue there


I understand that Ctrl+R is "Reload" & Ctrl+Shift+R is "Reload (Override Cache)", but why have both F5 and Ctrl+F5 **also** be "Reload"?

And even if I'm misunderstanding it and Ctrl+F5 is actually just another way to do "Reload (Override Cache)", that's still a redundancy for both. While I can understand the engineering need for component redundancies, I don't think that principle even applies here.

Can someone clear this up for me? Am I missing a crucial part of the rationale here, is it just a remnant of an earlier version of Firefox where it filled a once-existent gap in functionality, or is this just another example of a decision made by someone that makes no sense to anyone else?

''locking as a duplicate of https://support.mozilla.org/en-US/questions/1073264 - please continue there'' I understand that Ctrl+R is "Reload" & Ctrl+Shift+R is "Reload (Override Cache)", but why have both F5 and Ctrl+F5 **also** be "Reload"? And even if I'm misunderstanding it and Ctrl+F5 is actually just another way to do "Reload (Override Cache)", that's still a redundancy for both. While I can understand the engineering need for component redundancies, I don't think that principle even applies here. Can someone clear this up for me? Am I missing a crucial part of the rationale here, is it just a remnant of an earlier version of Firefox where it filled a once-existent gap in functionality, or is this just another example of a decision made by someone that makes no sense to anyone else?

Diubah oleh the-edmeister

All Replies (3)

more options

On laptop keyboards, function keys (F1 to F12) are often used for hardware settings (screen brightness, speakers volume…) so you can't use directly F5 key to reload a web page.

Function keys can be used with key combination, Fn + F5 for refreshing, but it isn't easy to do it without move your left-hand when your are taping.

Shortcut Ctrl + R is more accessible in this case.

more options

So it's the 2nd thing I mentioned—that it stems from an earlier time (and I suppose a present time, too :P ) when most keyboards were full keyboards, to be used with a desktop. Right?

more options

Firefox is a multi platform application and not all key sequences are available on all platforms, so in some case there is more than one way to do things. There are also (long lasting) platform conventions that Firefox obeys.