I agree with this. Accidentally going back when you lose focus on a text field is super annoying.
Chrome removes Backspace to go back
231–240 of 594 posts
Re: Chrome removes Backspace to go back
#232Anyone want to place bets on how long till Firefox copies them?
[deleted]
Re: Chrome removes Backspace to go back
#233Chrome / Chromium have a habit of making these arbitrary changes that seriously annoy some (arguably small) percentage of their users, while claiming that it makes it simpler / better for everyone else, while explaining impatiently why it's infeasible to make the now missing feature a configuration option. Evidently the kinds of people that can't be bothered going into the Advanced Configuration Settings page would b…
The backspace thing has gotten attention more than ever on sites like Reddit. I have routinely seen posts complaining about it and the spacebar key doing behaviors that users never ever intended. For example, pressing space and then accidentally scrolling down which wasn't their intention at all, but is the behavior of space. I think some of those complaints reaching the front page of reddit may have helped spur this…
I'm gonna be majorly pissed if they disable space bar scroll. I use that quite literally constantly while I'm browsing. It is the scrolling method I use 99% of the time.
Backspace to go back, OTOH, I was aware of, but I doubt I ever wanted. Alt-Left is easier to use because it's less modal. Still bothers me in general when devs screw with established defaults.
Re: Chrome removes Backspace to go back
#234Because adding customizable keybinds is too difficult? Hell, if configs looking scary to normal users is a problem why not just have a json/sqlite/whatever file in the profile directory?
Re: Chrome removes Backspace to go back
#235This feels a bit like how Esc was nerfed over the years in Firefox and others until it essentially did nothing. It used to mean STOP. All sockets were closed, the page stopped loading, and I think way waaay back, even animated gifs stopped cycling and JavaScript timeouts and intervals were cancelled. Single-page webapps were the death of Esc, it was too confusing to users to have a page suddenly hang because they pre…
Or maybe, it is well past time for browsers to have two concepts: “page” and “application” windows.
That way, web sites that are really trying to be applications can have one set of logical keystrokes, default security models, etc. and plain web pages can have another set. They could be further distinguished by some kind of difference in window frame.
Re: Chrome removes Backspace to go back
#236I wonder if this is in any way related to the exceptionally annoying thing on google.com, where if you hit backspace it doesn't navigate back, but starts removing characters from your search. It does this with other keypresses too, presumably so you can just keep typing till you find whatever you're looking for, but it's a flagrant disregard for my action of moving focus from the input field.
In any event, I use backspace to navigate back all the time, so this is sure to annoy me to no end. Especially since I use multiple browsers, and it'll be hard to break habits. Ah well..
Re: Chrome removes Backspace to go back
#237Wontfix - just apply the worst possible, cruddy fix and shut down discussion.
Forgive me if I do not applaud.
Re: Chrome removes Backspace to go back
#238One more plus for Vivaldi.
Re: Chrome removes Backspace to go back
#239I'm going to take a somewhat contrarian view and say, "Thank you, Chrome developers."
It's always easy to tell apart the people who know shortcuts from the people who don't, if you watch them use their computers. Someone with a few shortcuts on tap will zoom around their monitors, switching between mouse and keyboard only when necessary.
But there are a few shortcuts and user interface quirks that are too outdated and weird, and only serve to surprise and annoy us. They herald from an earlier age when people were still figuring things out in new UI paradigms. For example, these days, you expect the scroll wheel to scroll up and down in a scrolling view. However, my coworker was changing some project settings in Visual Studio the other day, and he tried to scroll through the settings while a drop-down menu in the settings had focus. It scrolled through the menu options, selecting them, instead of scrolling through the view. He had to cancel the changes he was making and open the window again, because he couldn't remember what was originally selected.
This is the worst kind of surprise. Something you thought was just supposed to let you look at different parts of the interface instead modified the data you were looking at. Backspace to go back is a similar surprise. It's supposed to delete text, but instead it can navigate away from a page entirely, if you are in the wrong state when you press backspace. For the same reason, I'm even getting sick of the old middle mouse button paste, since it's too easy to press when I'm scrolling.
Forward and back navigation are already mapped to alt + left and right arrow. Let's reserve backspace for deleting text. (I'm not happy that it sometimes means "navigate up a level", but that might tell you what kind of computer I had growing up.)
Re: Chrome removes Backspace to go back
#240I think comment #32 ( https://bugs.chromium.org/p/chromium/issues/detail?id=608016... ) is worth highlighting: If you can fill out a formular field correctly without losing focus, you are not part of Chrome's target audience. edit: Had to type this four times due to accidently going back.
Hah, that's funny! But also, comment #35 is on point:
> 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...)
I never have this problem in Safari, and I use backspace all the time for navigating back.