You’re at your PC or laptop, just about finished with that new G+/facevillebookspacetweetle post. You go to correct a little typo and instead of a single backspace your browser decides to go back an entire page. What the front door?! This happens because apparently you clicked somewhere on the browser window that wasn’t for text entry so the browser will then interpret the backspace key as “go back one page” and poof goes *all* your entered text. :|
Let’s get this fixed.
Firefox users can navigate to “about:config” without the quotes in the address bar and accept the warning prompt. Begin typing the word “backspace” in the search box on the config page and find the “browser.backspace_action” key. The default value is 0, double click and change this to 2.
It appears that most Chrome users are using the extension BackspaceMeansBackspace to handle the job though in the official Chrome store there’s a poorly rated extension (2 stars) named Backstop that you could try out if you’re feeling like a rebel.
There is one solution on Windows by using AutoHotKey with the following script:
#IfWinActive, ahk_class Chrome_WidgetWin_1
Though it requires the AHK framework and having a process running to achieve the end goal, it does get the job done.
Linux users aren’t totally out in the cold as there is an extension that is supposed to handle this in Chrome for you guys. You can try it out here.
With the new rage being all about cloud computing, we users are spending more and more time working in web browsers. If the developers of these browsers want us to use their products, they may want to consider implementing something so basic as this. This is a relic of browser programming standards and needs to be retired. We interact with our browsers much more now than just telling them to go forward and back.