MatSeFi
Pretty sure Mozilla has the numbers on how many installations each OS has, so it’s probably a legitimate decision. HOWEVER, if they want to maintain their position on Linux, I highly recommend changing the default behavior of Ctrl+Shift+C to match how it works in Helium, where it simply copies the selected content instead of opening Developer Mode, which cannot be closed again using the same keystroke.
Feb 19 at 12:47pmWeb
Show threadreisubFeb 19
You can change that in about:keyboard in the new Firefox versions
Show threadMatSeFiFeb 19
Absolutely, all behavior can be changed somehow. But the default defines the product :)
Show threadhalcyoncmdrFeb 19

Ah the classic Linux community response to any complaint.

  • The default either actively ignores what every other software does or purposely uses something other than everything else for no apparent reason.
  • Someone brings up the fact that it makes no sense why it’s different and how it makes the user experience worse.
  • Someone else recommends a half baked solution that still doesn’t really solve the problem and doesn’t address the fact that the specific weirdness being default is the issue. So it ignores the actual complaint and only provides a half solution.
  • Nothing is ever done to address the issue and it remains for decades constantly annoying new users and being one of thousands of small issues that turn potential curious new users away as they accumulate.
    • Show thread1984Feb 19

    Why is that persons response considered the community response?

    Ive been using Linux for 20 years so… Can we change that shortcut please?

    Show threadcadekatFeb 19

    Proposing a fix is better than no fix? I didn’t know it was possible, and now I’m looking into it.

    Changing the default is a social issue, so of course it’s more difficult than changing one’s current setting.

    Show threadfrongtFeb 19
    The fuck you want us to do about it? We don’t have commit access to firefox’s codebase.
    Show threadIrateAnteaterFeb 19

    I doubt they’ll change that, since Ctrl+Shift+C also opens the dev console on chromium based browsers on Windows (just tried it with Chrome and Edge). Not sure if that’s the behavior on Linux, since I only use Firefox there.

    Also, I really doubt that Ctrl+Shift+C behavior is going to factor into people’s decision anyway. That’s a very niche problem to have.

    Show thread9488fcea02a9Feb 19

    Can confirm ctrl-shift-c opens dev console

    I keep mixing up the shortcuts because ctrl-shift-c is copy in the KDE terminal

    Show threadMatSeFiFeb 19
    This behavior isn’t unique to KDE’s Konsole; many others share it. Since Ctrl + C performs an entirely different function in most Linux terminals/shells, Firefox’s default behavior feels out of place. It’s admittedly a niche problem, but to me, it looks like an ‘alien’ in the Linux world.
    Show threadIrateAnteaterFeb 19

    Unless Google’s search AI lied to me (and surely it would never do that) this is all Apple’s fault anyway. They are the one’s that highjacked Ctrl+c for the copy function.

    Unfortunately, that has become ingrained now everywhere other than the Linux terminal. And as Gui interfaces have improved over the years, average users are spending less time there, and Ctrl+shift+c has become the option that feels out of place.

    Show threadMatSeFiFeb 19
    Yeah potentially it would be easier/more concise if I’d adjust my terminal/shell to remap the crtl+c , crtl +shift +c behavior instead of demanding the whole world revert a decision made in the last century.
    Show threadjqubedFeb 19
    But copy is Command+C on macOS and iOS, not Ctrl+C. Maybe in the Classic Mac OS days, but I doubt they would’ve made such a significant change moving to OS X.
    Show threadsystemglitchFeb 19
    Also incentivizes people to not use it.
    Show threaddreamkeeperFeb 20
    Ctrl-Shift-C directly opens the element inspector. CTRL-SHIFT-I opens the dev tools with the inspector turned off.
    Show threadmyrmidexFeb 19
    Great suggestion, that is one of my gripes as well. Makes copying between terminal and browser just that tiny bit annoying.
    Show threadwoop_woopFeb 19
    Why?
    Show thread1984Feb 19
    Yeah the person who put Developer Mode on that shortcut… Must have never used linux.
    Show threadneo2478Feb 19
    What’s wrong with Ctrl+C to copy? Its the default shortcut on pretty much everything except terminals.
    Show threadMatSeFiFeb 19

    Whats wrong with using the metric system to represent quantities? Its the default on pretty much everything except fueling planes or operating satellites. /s

    The conflict arises from having two different defaults for the same action. Since users frequently switch between these environments, the lack of a universal shortcut causes constant friction.

    Gimli Glider - Wikipedia

    Show thread8uurgFeb 19

    The key issue is that the request is to change behavior in one place (browser) to match that of a rare case (terminal), causing a mismatch with the frequent case (office suites, mail programs, …). The terminal is the odd one out, not the browser, and ought be the one to change the default for the reason you provide.

    In practice, a terminal is a special case and not just a text input window, and current convention is that Ctrl + C aborts / cancels.

    (You could of course have a duplicate hotkey, but now you are inconsistent w.r.t. other browsers, and there will be someone else who will be annoyed by the difference)

    Show threadKornblumenratteFeb 21
    Actually, Ctrl+C is the ASCII Code for the control character ETX (End of Text) since the early 60s. This is not a hotkey but a control character. To change this system, you’d have to change not only dozends of terminal emulators and the kernels of all unixoid operating systems, but at least ANSI, Unicode and Posix, too. And Windows, by the way - even Microsoft uses ctrl+c in both cmd.exe and powershell to kill the running process.
    Control character - Wikipedia

    Show thread8uurgFeb 21

    To be similarly pedantic: Ctrl+C is a hotkey that send the corresponding ASCII code to signal something, it is not an ASCII code itself.

    You could have the same character be sent by using Ctrl+Q (if you were to remap it), and not break compatibility with other processes while doing so: the codepoint being sent would be the same. From a technological perspective there is nothing special about the key combination Ctrl+C specifically, but altering this behavior in a terminal absolutely wreak havoc on the muscle memory of terminal users, and altering it’s behavior in a text editor on everyone else’s.