News for hackers. Stuff that matters.
Re:Chrome removes Backspace to go back by mstade on Thursday May 19, 2016 @01:08PM (#11731718)
But there are better solutions. Comment #35 in that thread actually provides one:

> The problem: Moving away from a form can result in data loss.

> Your solution: Make it harder to move away.

> The correct solution: Cache tab history completely and make it easy to move forward and backward in a tab's history by reusing cache and maintaining form contents.

(Source: https://bugs.chromium.org/p/chromium/issues/detail?id=608016...)

Safari does this, for instance, and yes it does happen that I accidentally the whole thing by hitting backspace, but it's OK because I know if I just go forward again, it'll all still be there – fully intact.

Re:Chrome removes Backspace to go back by eslaught on Thursday May 19, 2016 @01:23PM (#11731853)
> > The correct solution: Cache tab history completely [...]

This is not a solution for the majority of users. The problem with keyboard shortcuts is that most users won't know what happened. All they'll know is that suddenly they're not on the same page any more, and then won't realize they've navigated backwards. Therefore they won't think to navigate forwards again, and they won't get back to their form data, even if it is cached.

This happens to me all the time in Emacs. I'll press something by accident, make major unintended changes to my file, and have no idea what I did. Fortunately, Emacs has a way to look up key presses, but this is a relatively advanced feature that typically doesn't exist in other tools anyway.

Whenever you have a feature with zero discoverability (e.g. essentially all keyboard shortcuts), you have to be very careful to avoid the "what did I just do?" phenomenon, even if you provide ways to get back to a previous state. I personally think this change by the Chrome devs is extremely reasonable in that regard.

Edit: I realize that these changes are aggravating to users who actually use them on a regular basis. However, please also realize that they are not zero-cost, because they do impose a constant and non-trivial burden on everyone else (especially in cases like backspace which are relatively easy to hit on accident).

Re:Chrome removes Backspace to go back by ultramancool on Thursday May 19, 2016 @02:52PM (#11732682)
> because they do impose a constant and non-trivial burden on everyone else (especially in cases like backspace which are relatively easy to hit on accident).

So make them an option and stop taking the Chrome route of stripping out everything that more advanced users use regularly.

Of course, this is why I run Firefox. I can do things like force OCSP enabled and get error pages when it fails - Chrome's solution was to call OCSP useless because their less technical users couldn't understand it.

Even Firefox has buried the option behind about:config and the scariest thing for me now is that we'll lose the control we get with current FF options and extensions as they "modernize" the browser.

Advanced users want this level of control.

Re:Chrome removes Backspace to go back by stouset on Thursday May 19, 2016 @03:58PM (#11733271)
There's a cost to this too, in terms of development effort. Yeah, one option isn't a big deal, but multiply this by the gajillion times that developers have to make a choice between something < 1% of their users want and what > 99% of their users want.

Backspace-as-back-button is not an "advanced feature". It's a hotkey that essentially no other software uses for the same behavior and one which conflicts crappily with the fundamental behavior of that key. It will take you, generously, a day to relearn the new hotkey. Instead you'd rather the developers maintain indefinitely an option and corresponding logic to support your existing use-case.

If you can't tell, my level of empathy for this kind of griping is roughly zero. Adapt to the new hotkey and save the complaining for something that actually matters.

Re:Chrome removes Backspace to go back by meatcider on Thursday May 19, 2016 @05:24PM (#11733991)
> It's a hotkey that essentially no other software uses for the same behavior

Except for Windows Explorer, but who uses that, eh?

Your level of empathy is immaterial to the conversation, but thanks for sharing.

Re:Chrome removes Backspace to go back by stouset on Thursday May 19, 2016 @08:16PM (#11734844)
Backspace on Windows Explorer goes up one directory, not back in your history.

In a not-at-all shocking turn of events, it turns out Alt-Left and Alt-Right are in fact the hotkeys for navigating backward and forward through history, so Chrome aligns perfectly with Windows Explorer in this regard.

Re:Chrome removes Backspace to go back by JoBrad on Thursday May 19, 2016 @09:28PM (#11735078)
No, it definitely serves as a back shortcut key, not up. http://windows.microsoft.com/en-us/windows/keyboard-shortcut...
Re:Chrome removes Backspace to go back by Arnavion on Thursday May 19, 2016 @08:58PM (#11734988)
Umm, Backspace in Windows Explorer absolutely does go back in history, unless this changed in Windows 8+ or something (testing on Windows 7 here).
Re:Chrome removes Backspace to go back by thaumasiotes on Friday May 20, 2016 @01:13AM (#11735672)
It goes back in history on windows 10 too. I never actually knew that, but hey.

I definitely believe removing backspace-to-go-back in the browser is the right choice. I did know about that one, solely because every so often I do it by mistake. The problem isn't that I lose data -- I don't. The problem is that this shortcut does nothing but cause me problems I don't want. I never want the functionality, and yet it keeps happening to me anyway because it's so easy to trigger unintentionally. There's no case for this shortcut continuing to exist.

Re:Chrome removes Backspace to go back by mrighele on Friday May 20, 2016 @01:44AM (#11735750)
Backspace used to go up one level up to Windows XP, if I remember correctly. Now you can go up one level with Alt+Up Arrow [1]

[1] http://windows.microsoft.com/en-us/windows/keyboard-shortcut...

Re:Chrome removes Backspace to go back by prof_hobart on Friday May 20, 2016 @03:56AM (#11736157)
Just tried it on my Windows 7 and it's quite definitely going up one level, not back in history.

If I've got a folder structure

1 | |--1.1 | |--1.2

And I click into 1.1 and then into 1.2, if I then press backspace I end up on 1 (the parent), not 1.1 (the previous in the history).

Re:Chrome removes Backspace to go back by cm2187 on Friday May 20, 2016 @09:09AM (#11737449)
Try going into C:\Folder1\Folder2\Folder3\Folder4\Folder5

Then click on "Folder3" to go directly to Folder3.

Then press BackSpace, you will go back to Folder5, not Folder2.

To go up the shortcut is ALT Arrow Up.

Now when there is nothing to go back to (you opened a sub folder directly), Backspace goes up instead of doing nothing.

Re:Chrome removes Backspace to go back by prof_hobart on Friday May 20, 2016 @09:27AM (#11737552)
Nope. Just done that, in a tree view. Took me to folder 2
Re:Chrome removes Backspace to go back by cm2187 on Friday May 20, 2016 @09:37AM (#11737629)
They must haved changed the behavior. I tried that on Windows 7 with a network drive.
Re:Chrome removes Backspace to go back by Arnavion on Saturday May 21, 2016 @07:31PM (#11746696)
prof_habart is pressing backspace while clicking entries in the tree view, which indeed treats backspace as going one level up, not one back in history. But that's not really relevant to this thread.
Re:Chrome removes Backspace to go back by ricksplat on Friday May 20, 2016 @07:29AM (#11736968)
In Windows 95 backspace went "Up One" but it's been "Back" ever since IE 4 introduced shell integration.
Re:Chrome removes Backspace to go back by cm2187 on Friday May 20, 2016 @09:06AM (#11737423)
No "Backspace" goes back, not up. Up is "ALT Up Arrow".
Re:Chrome removes Backspace to go back by ultramancool on Thursday May 19, 2016 @04:20PM (#11733450)
Sure, I understand your argument, but this is what addons are for.

Users who want it can install an addon for it.

Chrome on the other hand has such weak addon APIs that they are often unable to achieve what's needed. Firefox seems to be moving in the same direction unfortunately.

I think it's worth it for those developers to at least maintain full addon APIs, even though there's a trade-off here it greatly increases the flexibility of the product.

Re:Chrome removes Backspace to go back by recursive on Thursday May 19, 2016 @07:17PM (#11734603)
Is it not actually possible to implement this with an addon? It seems possible with a small script embedded in each page. If an addon can't do this, what could it possibly actually do?
Re:Chrome removes Backspace to go back by ultramancool on Thursday May 19, 2016 @08:34PM (#11734906)
In this case yes it should be, but I was getting at a larger problem - try to do this with something like Tree Style Tabs, DownThemAll, etc.
Re:Chrome removes Backspace to go back by HappyTypist on Friday May 20, 2016 @05:33AM (#11736546)
This can be done via an addon
Re:Chrome removes Backspace to go back by smoothdeveloper on Friday May 20, 2016 @03:57AM (#11736169)
alternatives:

* alert if any form filled by user wasn't submitted (in case site doesn't do that already)

* let 99% of user who don't know what they did (they are in minority compared to number of times backspace is pressed to actually navigate back) retype their form if they don't navigate forward (which recovers their input, or should)

* add a third hand to human race so it doesn't take all the hands to navigate back from keyboard

* lure lenovo to restore the back / forward keys on thinkpads and make that implemented on most keyboards

Re:Chrome removes Backspace to go back by Nexxxeh on Friday May 20, 2016 @06:38AM (#11736792)
>lure lenovo to restore the back / forward keys on thinkpads and make that implemented on most keyboards

The number of times I've accidentally hit the back-a-page button on my old X201, and wiped my in-progress form entry...

They smooshed those keys right around the arrow keys. The arrow keys I use to jumping around text.

That's worse than having a dual-use for backspace to me.

Backspace is far enough away that it's not hit by accident.

Re:Chrome removes Backspace to go back by smoothdeveloper on Friday May 20, 2016 @07:39AM (#11736998)
You can hit the other "forward" key to recover everything in a good browser and/or websites which don't do silly things (99.99% of cases).

It really feels chromium team should install telemetry:

* how many unsubmitted forms edits lost by mistake

* how many backspace keystroke to do "history-back"

They should also consider alt-gr + left as "back-history", using two hands for this could be avoided this way.

Re:Chrome removes Backspace to go back by saalweachter on Friday May 20, 2016 @09:29AM (#11737566)
Yes, because "Chrome phones home with all form data/keystrokes" wouldn't hit the top of HN.
Re:Chrome removes Backspace to go back by jamespo on Friday May 20, 2016 @07:28AM (#11736963)
Hitting them by accident is very rare for me - I love them on my x220, even more so when you can map them in emacs to switch buffer.
Re:Chrome removes Backspace to go back by code_sloth on Friday May 20, 2016 @06:29AM (#11736761)
> ... my level of empathy for this kind of griping is roughly zero. Adapt to the new hotkey and save the complaining for something that actually matters.

It's absolutely amazing how many comments (500++ as I write this) that this "news" generated.

Re:Chrome removes Backspace to go back by amluto on Thursday May 19, 2016 @08:50PM (#11734958)
I disagree here. Some shortcuts simply suck. Backspace to go back is one. This is because backspace is very useful and means something different when a text field is focused. It would be like using just plain Q to quit.
Re:Chrome removes Backspace to go back by Doctor_Fegg on Friday May 20, 2016 @07:37AM (#11736990)
On OS X, Command-left arrow means something different when a text field is focused, too. It means "go to the start of the line".
Re:Chrome removes Backspace to go back by pantalaimon on Friday May 20, 2016 @05:37AM (#11736558)
ctrl + q to quit is bad enough, it's right next to ctrl + w to close a tab
Re:Chrome removes Backspace to go back by jeeva on Friday May 20, 2016 @06:33AM (#11736774)
And Ctrl + Shift + W to close a window. Ugh. Lots of accidental closures...
Re:Chrome removes Backspace to go back by ryuuchin on Friday May 20, 2016 @04:13AM (#11736255)
> Chrome's solution was to call OCSP useless because their less technical users couldn't understand it.

OCSP introduced a non-trivial delay (cited as ~300ms to a second) and there are also privacy concerns with it as well[1]. There's also the fact that it's set to soft-fail when the OCSP servers can't be contacted making it useless in that case[2].

Even if we ignore the above reasons for its exclusion from Chrome they do provide CRLSets which provide similar functionality but are pushed via browser updates (supposedly it's updated daily which makes it faster than OCSP). I'm not sure it's fair to say that they called it "useless because less technical users couldn't understand it". How else can CRLSets be explained then?

[1] https://www.imperialviolet.org/2012/02/05/crlsets.html [2] https://www.imperialviolet.org/2014/04/19/revchecking.html

Re:Chrome removes Backspace to go back by ultramancool on Saturday May 21, 2016 @10:41AM (#11744822)
> There's also the fact that it's set to soft-fail when the OCSP servers can't be contacted making it useless in that case[2].

Yes, notice that I called for OCSP force/required, not just OCSP soft-fail. I've been running OCSP required for years and never had any noticeable slowdown. Maybe there's one on the first connection of the day to a site or something?

Chrome's CRLSets are extremely limited and cannot begin to capture the full number of domains which have been revoked. They can get the most popular sites and that's about it.

OCSP stapling is the superior solution which will solve this in Chrome and other browsers, but for now OCSP is the only reasonable solution in a world where millions of SSL certificates have leaked and been revoked and you care about your privacy. CloudFlare alone revoked millions of certificates. These have indeed not all made it into the CRLsets.

An excellent summary of the problems is here: https://www.grc.com/revocation/crlsets.htm

Chrome's CRLsets contain less than 1% of current revoked certificates. I can't in good faith call that a valid solution to the problem.

Re:Chrome removes Backspace to go back by ryuuchin on Sunday May 22, 2016 @04:15AM (#11747759)
There is still a non-trivial privacy issue with the OCSP checks although OCSP stapling does address that problem. The Chrome situation does leave something to be desired although I can sort of understand where they were coming from from the aspect of it being confusing. It is worth noting that only the setting on the settings page has been removed. You can still enable OCSP checks and OCSP forcing through the enterprise settings[1][2]. Also worth noting is that I believe they have only disabled OCSP checks, OCSP stapling should still work correctly if the server supports it.

[1] https://www.chromium.org/administrators/policy-list-3#Enable...

[2] https://www.chromium.org/administrators/policy-list-3#Requir...

Re:Chrome removes Backspace to go back by snaky on Thursday May 19, 2016 @06:40PM (#11734423)
> and the scariest thing for me now is that we'll lose the control we get with current FF options

That seems unstoppable for a long time now. There's no browser for power users in modern world.

Re:Chrome removes Backspace to go back by tomc1985 on Friday May 20, 2016 @12:32AM (#11735553)
Wasn't there a Firefox fork that's keeping XUL and XPCOM and all that? Pale Moon?
Re:Chrome removes Backspace to go back by JoBrad on Thursday May 19, 2016 @09:35PM (#11735102)
Vivaldi? I haven't used it recently, but it seems top be aimed at this group
Re:Chrome removes Backspace to go back by 0942v8653 on Thursday May 19, 2016 @10:02PM (#11735178)
Not at all, it's closed source
Re:Chrome removes Backspace to go back by 746F7475 on Friday May 20, 2016 @04:29AM (#11736297)
> So make them an option and stop taking the Chrome route of stripping out everything that more advanced users use regularly.

Did you really use backspace and "move back" on regular basis? Why? You most likely aren't browsing the web with just your keyboard, so unless you are a leftie it requires you to either move your hand back to keyboard or move your hand across the whole keyboard and why would you do either of these when you can just move back with your mouses thumb button?

Re:Chrome removes Backspace to go back by pkamb on Friday May 20, 2016 @01:58PM (#11740001)
As a ThinkPad external keyboard user it's my primary navigation to go Back. TrackPoint, no mouse. Primary scrolling navigation is the Home/End/PgUp/PgDn group. Backspace for Back fits amazingly in this workflow.
Re:Chrome removes Backspace to go back by Doctor_Fegg on Friday May 20, 2016 @07:38AM (#11736995)
Where's the "thumb button" on an Apple Mighty Mouse?
Re:Chrome removes Backspace to go back by 746F7475 on Friday May 20, 2016 @11:59AM (#11738892)
Well, maybe it's time to stop using inferior shit products and buy a proper mouse. Any $20 mouse from your local department store has at least one button to press with your thumb.
Re:Chrome removes Backspace to go back by Dayshine on Friday May 20, 2016 @10:50AM (#11738231)
>with your mouses thumb button?

Because I'm far more likely to accidentally press the mouse thumb button, hence it's rebound.

Re:Chrome removes Backspace to go back by nitrogen on Thursday May 19, 2016 @02:16PM (#11732348)
Keyboard shortcuts are only undiscoverable because apps stopped listing the shortcuts next to the menu items.
Re:Chrome removes Backspace to go back by civilian on Thursday May 19, 2016 @03:56PM (#11733248)
110% yes. I've been playing Stellaris, and they actually put hotkey references in the tooltip! I can't do everything with the keyboard, but I'm doing way more than I was. Hotkeys are great and we should encourage more tooltips & labels with them. Not just in videogames, but in anything that could benefit from hotkeys.
Re:Chrome removes Backspace to go back by DonHopkins on Thursday May 19, 2016 @04:22PM (#11733473)
Stellaris is magnificent! It's incredibly deep and complex, but it has a great user interface, and they've been totally thorough about putting helpful color coded pop-up tooltips everywhere there's something interesting to point at, giving you information about every icon and button, revealing keyboard shortcuts, and telling you one or more tasks that you need to do to first to enable disabled buttons.

I really hate the cargo-cult tradition of disabled menu items that don't tell you anything about why they're disabled, or what you can do to enable them. That's so frustrating, it's like the computer knows something you want to know to do what you want to do, but it won't tell you, because you have to guess.

Even better: Clicking on a disabled item should start a dialog to help you satisfy the prerequisites before performing disabled the action, instead of just ignoring you or telling you to go somewhere else.

I was able to trade alien pets to a highly advanced xenophilic civilization who wouldn't otherwise talk to me, in exchange for civilian access to their space! I felt like Harry Mudd sneaking through Klingon space with a space shuttle full of tribbles!

Re:Chrome removes Backspace to go back by LoSboccacc on Thursday May 19, 2016 @05:12PM (#11733900)
Jeez if stellaris is considered deep what'd be your opinion on distant world: universe?

Mind you I'm enjoying it but many parts fall extremely flat. Like corvette balance and topped war scores.

Re:Chrome removes Backspace to go back by emp_zealoth on Thursday May 19, 2016 @08:50PM (#11734957)
Apparently a game called M.O.R.E. is lurking around, promising all kinds of crazy depth (I'm super sad how bad SotS 2 was :( )

I totally agree that Stellaris kind of falls flat atm IMO - the foundation is rock solid, the game looks gorgeous and the music just blows you away...but then you play on Hard and literally nothing happens for 6 hours. Eventually a war happens and instantly degenerates into a massive my-blob-chasing-your-blob-benny-hill-nonsense :/ And you can't even achieve anything because of 100 warscore limit! Apparently there are serious improvements coming soon though(Allegedly a lot of content wasn't polished enough before the deadline so minimal viable product happened)

Re:Chrome removes Backspace to go back by eropple on Thursday May 19, 2016 @09:42PM (#11735118)
> massive my-blob-chasing-your-blob-benny-hill-nonsense

In our attempts at multiplayer, we've already reduced ourselves to calling this "Yakety Saxxing".

Re:Chrome removes Backspace to go back by thaumasiotes on Friday May 20, 2016 @01:16AM (#11735679)
> Eventually a war happens and instantly degenerates into a massive my-blob-chasing-your-blob-benny-hill-nonsense :/

You might be surprised by some actual wars.

Re:Chrome removes Backspace to go back by emp_zealoth on Friday May 20, 2016 @02:47AM (#11735944)
I would go out on a limb and stipulate that letting an enemy army free reign behind one's lines is a sure way to get rekt. It's just in Stellaris it takes a year for anything to happen from bombardment... It really needs some improvement to wartime movement
Re:Chrome removes Backspace to go back by Dayshine on Friday May 20, 2016 @10:53AM (#11738265)
It's the first version of a Paradox game, give it a few expansions.

EU4 has taken close to a decade to get where it is.

Re:Chrome removes Backspace to go back by TeMPOraL on Friday May 20, 2016 @10:06AM (#11737847)
Emacs has a nice way of teaching people shortcuts. If you invoke a command via some menu or M-x full-command-name that has a shortcut bound to it, you'll get a message in the minibuffer saying "You can also run full-command-name with: shortcut". It's a very non-invasive way to teach people shortcuts just-in-time.
Re:Chrome removes Backspace to go back by civilian on Friday May 20, 2016 @02:12PM (#11740114)
Huh, that is awesome. As a novice vimpire I'd love to figure out a teaching tool like that for vim. Vim doesn't really have a menu-- but maybe something that recognizes what series of edits you just made and suggests a shortcut?

(I.e. "You just traveled to the end of a line and deleted a ". You could have done 'A[esc]dw' or whatever it is. Like I said, I'm bad at vim over here.)

Re:Chrome removes Backspace to go back by chc on Thursday May 19, 2016 @02:35PM (#11732504)
In the case of "Go back," there are two or three keyboard shortcuts in most browsers, of which I'd guess backspace is probably the least (intentionally) used.
Re:Chrome removes Backspace to go back by panglott on Thursday May 19, 2016 @03:33PM (#11733061)
"Backspace" to go back was new to me, and just sounds like a terrible idea, you'd be accidentally deleting things all the time.

Firefox does not have "Go back" accessible through the menu, although the "Backspace" keystroke works. Chrome also does not have a "Go back" accessible through the menu that I can find. Hovering over the Back button shows how to click to access history.

Re:Chrome removes Backspace to go back by marcosdumay on Thursday May 19, 2016 @05:15PM (#11733918)
> although the "Backspace" keystroke works

Does not work for me, FF 38. This feature used to throw me out of forms all the time, there has been a couple of years that it stopped.

Now the only FF keystroke that annoys me is the CTRL-q for closing the window, that conveniently is just by the side of CTRL-w for closing the tab, and does not save the window state.

Re:Chrome removes Backspace to go back by cpeterso on Thursday May 19, 2016 @09:44PM (#11735127)
> Does not work for me, FF 38. This feature used to throw me out of forms all the time, there has been a couple of years that it stopped.

Are you on Linux? Backspace to go back only works on Windows and OS X because this behavior was apparently un-Linux-like. You can change this behavior with the browser.backspace_action about:config pref:

http://kb.mozillazine.org/Browser.backspace_action

Here is a Firefox bug to make Backspace work on Linux Firefox the same as it does on Windows and OS X:

https://bugzilla.mozilla.org/show_bug.cgi?id=986982#c6

Re:Chrome removes Backspace to go back by nsm on Thursday May 19, 2016 @09:39PM (#11735114)
Re:Chrome removes Backspace to go back by nommm-nommm on Thursday May 19, 2016 @10:29PM (#11735234)
>does not save the window state.

Do any of these options work to get your state back after accidentally closing the browser?(1) Is control-w significantly different than pressing the x on the Window? Just curious.

(1) https://support.mozilla.org/en-US/kb/how-do-i-restore-my-tab...

(Might not work if you delete history on close)

Re:Chrome removes Backspace to go back by nitrogen on Friday May 20, 2016 @01:05PM (#11739518)
Closing a window can sometimes be undone by pressing Ctrl-Shift-N, even after a browser restart.
Re:Chrome removes Backspace to go back by chc on Thursday May 19, 2016 @03:52PM (#11733211)
Weirdly, these commands are in the menus for the Mac version (they're the second and third commands in the History menu), but the versions for Windows and Linux don't seem to have them.
Re:Chrome removes Backspace to go back by panglott on Thursday May 19, 2016 @04:22PM (#11733477)
I was wondering what the Mac versions did, since there's no Backspace. "Press Delete to go back"?
Re:Chrome removes Backspace to go back by chc on Thursday May 19, 2016 @04:46PM (#11733696)
The key is labeled as delete, but it's functionally the same as backspace and it does indeed make you go back in browsers.
Re:Chrome removes Backspace to go back by aeosynth on Thursday May 19, 2016 @02:26PM (#11732436)
Menu items are only discoverable to those who take the time to look through them; the majority of users do not.
Re:Chrome removes Backspace to go back by chc on Thursday May 19, 2016 @02:35PM (#11732511)
Isn't that what "discoverable" means? That if you look for it, you'll find it?
Re:Chrome removes Backspace to go back by wastedhours on Friday May 20, 2016 @05:44AM (#11736588)
Intrigued by "This is not a solution for the majority of users." - do we really know what percentage was intended? If we're going by anecdotal, then everyone I know fully uses backspace to go backwards, including parents and non-technically minded colleagues. Would have assumed that if you go backwards by accident, the obvious solution is to go forward again, no?
Re:Chrome removes Backspace to go back by warfangle on Friday May 20, 2016 @06:12AM (#11736705)
Given the state of usability labs at Goog, it's probably a substantial and statistically relevant percentage.
Re:Chrome removes Backspace to go back by mstade on Friday May 20, 2016 @11:06AM (#11738398)
> This is not a solution for the majority of users. The problem with keyboard shortcuts is that most users won't know what happened. All they'll know is that suddenly they're not on the same page any more, and then won't realize they've navigated backwards. Therefore they won't think to navigate forwards again, and they won't get back to their form data, even if it is cached.

If this is true, it's a very convincing argument – I'd buy it for a dollar. In any event, my personal preference is to keep this backspace behavior, and my browser of choice (Safari) implements this caching perfectly.

At this point, not only am I ok with the accidental back navigation, but also I actively rely on things working this way. For instance, here on HN I routinely hit back and forward to see what people wrote, and Safari keeps my drafts perfectly well.

Re:Chrome removes Backspace to go back by drostie on Thursday May 19, 2016 @01:17PM (#11731794)
This can be a little dicey when AJAX was used to render the form that you're thinking about submitting; for a browser to Do It Right they may need to cache complicated stuff like (a) the entire DOM and (b) the entire state of the JS interpreter at the moment navigation began away from the page. Even if we only do this on backwards navigation and immediately trash it when we navigate forwards to a new location, it still sounds to a developer's ear like a memory leak waiting to happen. It might be mitigated if you store no more than, say, 10 pages back.
Re:Chrome removes Backspace to go back by iopq on Thursday May 19, 2016 @01:33PM (#11731965)
when you get the form back up, the browser should fill it because it should remember the form state from earlier

alternatively, just don't browse away when you have something filled in a form - just ask the user if they meant to do that

Re:Chrome removes Backspace to go back by shkkmo on Thursday May 19, 2016 @01:57PM (#11732169)
Detecting and/or saving "something filled in a form" is hard to do with 100% accuracy across all the oddly implemented forms out there. While I feel it has slowly gotten better over the years, especially on well implemented pages, it is still a common enough issue that another solution was needed.

I do wish they had mad a user configurable flag rather than forcing people to use plugins to re-acquire functionality they had before.

Re:Chrome removes Backspace to go back by onion2k on Thursday May 19, 2016 @05:09PM (#11733867)
I'm not sure why it'd be hard. "If there's a dom element that's an input of any time, and the user has focused it at any point, ask for confirmation on page exit" would work fine. The only case where I can see it being an issue would be a site that uses a select element as a menu, but I've not seen any do that in years.
Re:Chrome removes Backspace to go back by PunchTornado on Thursday May 19, 2016 @05:58PM (#11734205)
I think it can easily get abused, just some hidden focused inputs
Re:Chrome removes Backspace to go back by onion2k on Friday May 20, 2016 @01:40AM (#11735738)
Browsers already have a pageUnload event that can block a user leaving until they confirm they want to. This would effectively be the same.
Re:Chrome removes Backspace to go back by makapuf on Thursday May 19, 2016 @03:35PM (#11733078)
Or maybe like just disable it if there is something to lose ie there is a form and I entered something in it with the keyboard
Re:Chrome removes Backspace to go back by Jtsummers on Thursday May 19, 2016 @03:51PM (#11733197)
That would be worse. Then the expected behavior (that backspace would navigate back) wouldn't occur because I'm filling in this form. Even though I've left the field (so backspace is captured by the tab and not the form field) and have decided to abandon the comment and go back to reading the thread.
Re:Chrome removes Backspace to go back by iopq on Thursday May 19, 2016 @05:47PM (#11734138)
you can just say "Cancel" or "Navigate away" in the dialog that comes up

if you have written a long paragraph it shouldn't just be lost because you accidentally pressed a key on your keyboard

Re:Chrome removes Backspace to go back by nkoren on Thursday May 19, 2016 @01:20PM (#11731829)
The web no longer consists of just static web pages and form data.

I build complex web applications, which are stateful in many ways that don't involve forms (and involve things like websocket connections, etc). There's no way that the browser could possibly recreate that state by going forward.

So web apps of any complexity must necessarily intercept the delete key and break its functionality. And to the extent that the web increasingly consists of such apps, it means that "delete to go back" has long since being a standard feature that users can count on. That's just a fact on the ground. Time to remove the expectation entirely.

Re:Chrome removes Backspace to go back by michalstanko on Thursday May 19, 2016 @02:16PM (#11732346)
Finally someone brought up the fact that web does not consist of static classic HTML forms only, HOWEVER I still think Chrome could just restore those that ARE static, and as for the forms that are rendered using client-side templates in single-page apps, their creators should store them as they're being filled, just like Gmail or Google Docs store what you're typing without you having to save it manually.

I incline to believe that users that were filling out long forms (and subsequently complaining about losing data because of hitting backspace) were filling out classic old-school static HTML forms, where automatic form restore by Chrome would certainly help.

Re:Chrome removes Backspace to go back by grncdr on Friday May 20, 2016 @07:59AM (#11737065)
I agree that automatic form restoration would be very helpful, but there's a huge space between classic HTML forms (where this is "easy") and single-page apps (where nobody really expects it to happen).

That space is where complex, dependent-on-javascript-for-no-good-reason forms live. The kind often encountered when dealing with financial & public institutions. It's unlikely that automatic form restore is going to work for a lot of these (especially multi-step wizards & the like) so preventing an extremely common accident seems extremely prudent to me.

Re:Chrome removes Backspace to go back by __david__ on Thursday May 19, 2016 @02:09PM (#11732278)
> There's no way that the browser could possibly recreate that state by going forward.

Of course there is—just don't delete anything immediately. All your state stays there like it's in its own (hidden) tab and gets lazily garbage collected "some time" later. If the user navigates back, there's nothing to rebuild as everything is still sitting there intact.

Re:Chrome removes Backspace to go back by chc on Thursday May 19, 2016 @02:37PM (#11732531)
While that would work, this seems like the path to "Firefox is too heavy and uses lots of memory."
Re:Chrome removes Backspace to go back by mstade on Friday May 20, 2016 @11:02AM (#11738361)
I don't know how Safari does it, but it works, is incredibly fast, and eats much less memory than Chrome. (My browsing habits suggest Safari is about 30-40% cheaper in terms of memory, but that's anecdata so truck loads of salt required.)

In any event, there are way too many replies to keep count of in this thread, but all I can say is that however Safari does it – it just works(tm). Accidental backspace has literally never been an issue for me since they implemented this. There are convincing arguments why backspace as a short cut is a bad idea to begin with, but old habits die hard, and I for one am very happy that Safari makes this work.

Re:Chrome removes Backspace to go back by brandon on Thursday May 19, 2016 @08:38PM (#11734920)
What do you do about WebSocket connections or hanging GETs? Do you lie to the page about whether its still being rendered visibly? Etc etc.

This all seems terribly expensive relative to removing a hotkey used by fewer than 1% of users.

Re:Chrome removes Backspace to go back by joelwilliamson on Thursday May 19, 2016 @07:13PM (#11734580)
People would quickly come to depend on their data not being lost when they leave a page, and then be very unhappy when sometimes it is lost.
Re:Chrome removes Backspace to go back by NDizzle on Friday May 20, 2016 @01:12AM (#11735667)
Complex web applications that have less functionality than what you are trying to replace.

Great work!!!

Re:Chrome removes Backspace to go back by nkoren on Friday May 20, 2016 @05:16AM (#11736483)
Last night I watched 19 engineers use my application to work collaboratively, in real-time, on a single canvas, to design a transport network for a city. That kind of functionality has never existed before, anywhere, and is a damned sight more important than preserving the idiotic "delete === go back" keybinding that 99% of the population doesn't even know exists and only ever triggers accidentally.
Re:Chrome removes Backspace to go back by mastazi on Friday May 20, 2016 @02:56AM (#11735977)
> that have less functionality than what you are trying to replace

How so? Can you elaborate?

Re:Chrome removes Backspace to go back by rayiner on Thursday May 19, 2016 @02:42PM (#11732587)
A modal shortcut key whose behavior differs depending on the content of the text-box that has focus is still a braindead UI feature that causes unnecessary surprise. Making the consequences of screwing up less severe doesn't change that.

There is no rational defense for overloading a single button with two totally unrelated functions (navigation and text input). It's a design wart that people are defending on inertia alone.

Re:Chrome removes Backspace to go back by jacobolus on Thursday May 19, 2016 @08:07PM (#11734824)
Keyboard shortcuts are horribly broken, because all of the common keys (tab, space, return, escape, etc.) and various other standard shortcuts have been overloaded with abandon over the years.

In a better world, there would be much clearer defined intermediate interfaces between keyboard hardware, operating system, and final software (e.g. the native app, system shortcut, or browser javascript) performing the action for the user. Every interface would be clean and straight-forward, and easy for the user to adapt to her preferences.

In the world we live in, there are a confusing mishmash of 6–7 intermediate layers, which differ on each operating system and keyboard, some of which can be partially adapted by the user, but many of which can’t. These layers are poorly defined, not understood by users, and reach into each-other with various ugly hacks, and they often co-opt each-other’s keyboard shortcuts in arbitrary and confusing ways.

Re:Chrome removes Backspace to go back by niels_olson on Thursday May 19, 2016 @01:19PM (#11731816)
Wait until you're filling out online mortgage documents, or a security clearance application, or some other high-stakes documents. You will not like the backspace to go back function. Your adrenergic nervous system will make sure of it.
Re:Chrome removes Backspace to go back by spacecowboy_lon on Friday May 20, 2016 @08:45AM (#11737294)
So you think filling out a security clearance form online is a good idea
Re:Chrome removes Backspace to go back by animeweedlord on Thursday May 19, 2016 @01:17PM (#11731791)
I think Chrome does this as well. The real problem is that it doesn't seem to work with dynamically created forms, and web devs ruined everything with client-side templating.

But along the same lines, I would like it if browsers waited 5 seconds before actually killing a tab that you closed. That would not only fix your problem (if you applied it to page history changes as well), but solve most accidental data loss problems, and most importantly for me, be the end to having to reload entire pages just because I held down Ctrl-W for too long.

Re:Chrome removes Backspace to go back by nitrogen on Thursday May 19, 2016 @02:17PM (#11732364)
Try Ctrl-Shift-T
Re:Chrome removes Backspace to go back by animeweedlord on Thursday May 19, 2016 @02:58PM (#11732746)
I'm well aware. I'm saying that the tab should appear to close but persist in the background for a short period of time so that I can Ctrl-Shift-T and get my untouched context back.
Re:Chrome removes Backspace to go back by chipperyman573 on Thursday May 19, 2016 @03:19PM (#11732943)
What if you're watching a video on youtube? Even if you mute it, the video will continue to play, and if you resume the video later, your saved time will be 5 seconds later than what you thought it was.
Re:Chrome removes Backspace to go back by animeweedlord on Thursday May 19, 2016 @04:09PM (#11733359)
Good point. It's times like these I wish there was proper separation between the "hyperlinked documents and dumb form-based UIs" web and the "jerry rigged universal app runtime" web.

EDIT: But if it were an option or an extension, I would gladly enable it to help for 99% of sites I use and either accept the occasional weirdness or blacklist it for Youtube et all

Re:Chrome removes Backspace to go back by icebraining on Thursday May 19, 2016 @07:10PM (#11734566)
The browser knows how to pause HTML5 videos. If it's Flash, just kill it off.
Re:Chrome removes Backspace to go back by nitrogen on Thursday May 19, 2016 @03:45PM (#11733144)
What are you losing when you use Ctrl-Shift-T?
Re:Chrome removes Backspace to go back by animeweedlord on Thursday May 19, 2016 @04:05PM (#11733328)
Even if everything is cached, there is an annoying delay while the tab is reconstructed and the server is pinged. Even for something as trivial as a directly viewing a single image.

That's my main pain point (I really do think about frequently), but if others are having problems with AJAX-generated forms or whatever, it would help them too.

Another example would be losing your place in on an infinitely scrolling page (yet another web anti-pattern) because you accidentally closed the tab. I would appreciate having a second to correct my mistake before I having to do the"scroll wildly for 30 seconds until it catches up to where I was" song and dance.

Re:Chrome removes Backspace to go back by phasmantistes on Thursday May 19, 2016 @02:55PM (#11732723)
Chromium already puts heroic effort into maintaining form state. Note that, a lot of the time, it works great. For example, here on HN, if you enter half a comment, go back, and then forward, your comment will be preserved.

But it is hard. No browser has succeeded in serializing full tab state: dom, forms, js, pending requests, etc. Chromium has been working on it and has large pieces of it but it is very very hard to get even close to fully correct.

You're letting perfect be the enemy of better.

Re:Chrome removes Backspace to go back by stevefeinstein on Thursday May 19, 2016 @01:37PM (#11732013)
This is the correct answer. However even this isn't enough. I would also remove backspace from going back a page. It should never have been a thing. Having a key that performs a function modally when the context isn't very clear, is just ripe for confusion. And confusing it has been as the fact that this issue was raised.
Re:Chrome removes Backspace to go back by dclowd9901 on Thursday May 19, 2016 @03:00PM (#11732767)
This can be dangerous behavior, or illegal behavior in the case of password fields or credit card information being retained (in JS, you can't backfill password fields, so I don't want my browser doing it with ephemerally cached info). I am fully willing to sacrifice something I don't use (and very few people rely on) over having to refill out a form or risk security to accommodate a very dated and almost unused behavior.
Re:Chrome removes Backspace to go back by lloeki on Friday May 20, 2016 @03:54AM (#11736144)
To me the worst offender is not loss of data (seriously this is just a web form) but loss of context. Having the current location change is disorienting to the user† especially when it's not the expected result.

IIRC Safari had some CMD+Backspace ("Clear history") that I kept on triggering the same way, as in a Cocoa text field it means "Clear from cursor to beginning of line"), but apparently they (thankfully) removed it too. The process, and resulting effect, was the same.

Basically in terms of usability this boils down to the key behaviour following an implicit mode (triggered by what's focused), making it hard to discover (or discovered the hard way) and unpredictable.

This is similar to Safari's braindead CMD+Z that does both "undo in a text{field,area}" and "reopen last tab".

† even though I myself know what happens I am taken aback every single time because it just breaks the flow, resulting in grievous annoyance. Therefore, props to the Chrome team.

Re:Chrome removes Backspace to go back by Margh on Friday May 20, 2016 @04:15AM (#11736260)
fun fact: when the dagger you've used to indicate footnotes is attached to a person (the user), this typically indicates that the person is now dead.

i thought you were applying some subtle commentary about the change until i saw you agree with it.

Re:Chrome removes Backspace to go back by dilap on Thursday May 19, 2016 @01:37PM (#11732014)
leaving a page is still traumatic, and caching is never perfect (passwords &c). honestly this was always an insane shortcut.
Re:Chrome removes Backspace to go back by dredmorbius on Thursday May 19, 2016 @03:25PM (#11733004)
I'd argue for both.

Caching local content as drafts-in-process does in fact make a great deal of sense.

How to present that poses a new set of UI/UX considerations. Perhaps not grave, but significant.

I do hold strongly that the "backspace to navigate* motif is either profoundly broken or tied to unacceptably weak state stickiness of editing content itself. It's a callousness, capriciousness, and lack of consideration on the part of browser developers to users concerns (as opposed to advertisers) which I'm very hard pressed to defend on any basis.

Re:Chrome removes Backspace to go back by psook on Thursday May 19, 2016 @06:29PM (#11734379)
Shortcuts for standard features should be configurable without extensions. The fact that none of the modern browsers implement this is shameful, not the specific choices they make with bindings.
Re:Chrome removes Backspace to go back by Fabroskii on Thursday May 19, 2016 @06:49PM (#11734464)
What about applications that contain a JS environment? Is this not lost when navigating away, unable to be rebuilt from cache by moving forward?

What if my application needs to do something during data entry that can't be replicated by auto-populating the fields?

I believe this is taking power away from web developers and putting it into browser developers. That's a bad thing.

Re:Chrome removes Backspace to go back by seanp2k2 on Thursday May 19, 2016 @06:45PM (#11734450)
For form recover, Lazarus is available for Firefox and Chrome and works wonderfully most of the time. It's saved my bacon on many occasions.
Re:Chrome removes Backspace to go back by ikeboy on Thursday May 19, 2016 @03:07PM (#11732826)
Or comment 34:

>Why not disable backspace only when some form has data entered? Why remove the feature in all cases when the reason only applies to some?

Re:Chrome removes Backspace to go back by Klathmon on Friday May 20, 2016 @08:20AM (#11737164)
Because then we have 3 different ways that the same key will work depending on the page (delete text, go back a page, do nothing?).
Re:Chrome removes Backspace to go back by debaserab2 on Thursday May 19, 2016 @02:34PM (#11732499)
Oh man, I can't even imagine the myriad of ways that functionality would fail in today's client side JavaScript apps.
Re:Chrome removes Backspace to go back by Shorel on Friday May 20, 2016 @06:35PM (#11742079)
Old Opera did this, before all the other browsers.

It still did not help them gain more than 4% marketshare.

Re:Chrome removes Backspace to go back by smegel on Thursday May 19, 2016 @03:01PM (#11732778)
Oh yes, then you click forward and JavaScript on the page wipes all the fields.

Good thinking 99.

Re:Chrome removes Backspace to go back by LoSboccacc on Thursday May 19, 2016 @05:15PM (#11733914)
"Correcter" solution: onbeforeunload handler
Re:Chrome removes Backspace to go back by te0x on Thursday May 19, 2016 @01:50PM (#11732115)
> Your solution: Make it harder to move away.

The more genuine way to phrase this would've been something like "Your solution: use different keys for moving away from a form and erasing data", which sounds a lot more reasonable