• @[email protected]
    link
    fedilink
    English
    1110 days ago

    https://support.mozilla.org/en-US/questions/1336330

    Is there a way to restore backspace button function in the newest version of Firefox, so when pressing it the previous page opened?

    This function was very helpful for me!

    To prevent user data loss when filling out forms, we’ve disabled the Backspace key as a navigation shortcut for the back navigation button. To re-enable the Backspace keyboard shortcut, you can change the about:config preference browser.backspace_action to 0. You can also use the recommended Alt + Left arrow (Command + Left arrow on Mac) shortcut instead.

    • Ernest
      link
      fedilink
      English
      510 days ago

      I understand the reasoning, but I really wish Firefox had configurable keyboard shortcuts.

      heck, everything should have configurable shortcuts. It’s an accessibility feature with an obvious curb cut effect.

    • Amju Wolf
      link
      fedilink
      English
      210 days ago

      The better UX could have been making this a regular option, and (by default) showing a warning dialogue if using backspace to navigate would clear out a form.

      • @[email protected]
        link
        fedilink
        English
        19 days ago

        Haven’t done much web UI, but I’m guessing that are too many way to skin the “form” cat to account for.

        In any case, first time I’ve read any reasoning on removing it. Chrome killed it long ago and I was using an extension to re-enable it. Probably could have done as I just did in Firefox, fiddle with the config.

        • Amju Wolf
          link
          fedilink
          English
          19 days ago

          Form and input elements are a very standard thing, and while you can certainly do crazy stuff with it, even a simple check if you typed into an input/textarea, or changed a select without submitting the form element, should be sufficient.

          I guess the problem might be detecting the submission (because oftentimes there’s custom logic for that) but maybe better just display the warning than lose data. Worst case you’ll just ignore it, best case the devs fix it so that it doesn’t show up when it shouldn’t.