Thank the gods! I can't imagine who ever thought backspace as back was a good idea in the first place.
Chrome removes Backspace to go back
131–140 of 594 posts
Re: Chrome removes Backspace to go back
#132So they applied the wrong fix, to a problem that had been solved a decade ago. The problem: Moving away from a form can result in data loss. Their solution: Make it harder to move away? The actual solution implemented more than a decade ago: Cache history completely and make it easy to move forward and backward in a tab's history while maintaining form contents.
The problem with that solution is, at least in my experience, that it doesn't really work reliably for most "rich" web apps , which are more and more common. (I understand that this is a controversial topic in its own light.)
I can understand where they're coming from, and I'd be fine with a browser extension. Hopefully the one a Chrome developer is working on[1] will be available before this Chrome release hits stable.
[1]: https://bugs.chromium.org/p/chromium/issues/detail?id=608016...
Re: Chrome removes Backspace to go back
#133Chrome / 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…
I'm primarily on Windows and that first feature annoys the heck out of me. I would rather scrolling stop or continue, but the snap-back when the mouse leaves a zone is irritating. I think the second is more of an optimization because when you click on the address bar you're most likely either copying or overwriting the URL. It's much less common to modify it. If you want a supremely annoying address bar, you should c…
I use the first feature constantly. If I'm reading reddit comments at the bottom of the page, I can scroll to the top and a part of the original post and then snap back to where I was. I think Chrome actually removed this for a day or two and it really annoyed me.
Re: Chrome removes Backspace to go back
#134Earlier quoted context omitted.
The file explorer address bar was one of the best features that were introduced in Vista IMO. If you're in folder "C:\foo\bar\baz\boz\" and want to go to "C:\foo\" it's just one mouse click. Or if you want to go to "C:\foo\bor" that's just two mouse clicks. Much faster than clicking "back" or "up" multiple times.
To add to this, I believe in Windows 10 (possibly 8?) you can actually move files to a grandparent folder by dragging it to the associated button in the breadcrumb bar. Going from memory since I couldn't reproduce this behavior in 7. Could also be wrong about 10; someone else should try it and confirm.
I just tested in Windows 10, and you're right, you can drag files to any of the parent directories in the address bar.
Re: Chrome removes Backspace to go back
#135Chrome / 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…
> clicking inside the URL bar selects the whole contents This is one of the annoyances on Windows. On Linux/OSX you can click and drag on the URL to select a portion of the string, but on Windows it auto-highlights the full string completely, forcing one to reclick again (slowly!) to highlight a portion. Also: right-clicking on a link in Linux/OSX auto-highlights the full link text so you can `Copy` or `Search on Goo…
> On Linux/OSX you can click and drag on the URL to select a portion of the string
Works fine on Windows. Just don't click into the address bar before dragging and everything works as you'd expect. With clicking first you have a selection, though, and dragging that will do drag & drop of text instead.
Re: Chrome removes Backspace to go back
#136So they applied the wrong fix, to a problem that had been solved a decade ago. The problem: Moving away from a form can result in data loss. Their solution: Make it harder to move away? The actual solution implemented more than a decade ago: Cache history completely and make it easy to move forward and backward in a tab's history while maintaining form contents.
The problem with that solution is, at least in my experience, that it doesn't really work reliably for most "rich" web apps , which are more and more common. (I understand that this is a controversial topic in its own light.) I can understand where they're coming from, and I'd be fine with a browser extension. Hopefully the one a Chrome developer is working on[1] will be available before this Chrome release hits stab…
Sadly implementing it as an extension is a security issue, as mentioned elsewhere plenty.
Re: Chrome removes Backspace to go back
#137Finally! I can get rid of my third party extension to get rid of this insane behavior.
Re: Chrome removes Backspace to go back
#138I might be the minority here, but I think that using the backspace to go back is counter intuitive. In my mind backspace is to delete something, and I always worry about that.
I suspect you are part of the silent majority. :)
Re: Chrome removes Backspace to go back
#139"We have UseCounters showing that 0.04% of page views navigate back via the backspace button and 0.005% of page views are after a form interaction. The latter are often cases where the user loses data. Years of user complaints have been enough that we think it's the right choice to change this given the degree of pain users feel by losing their data and because every platform has another keyboard combination that nav…
Your usability study methodologies are worthless if they conclude that "backspace back" is worthless.
It's the first thing I'm always enabling on every new Firefox installation since they disabled it by default several years ago.
And with sufficiently large user base, even 0.04% means "lots of people being pissed off now".
Re: Chrome removes Backspace to go back
#140Earlier quoted context omitted.
The problem with that solution is, at least in my experience, that it doesn't really work reliably for most "rich" web apps , which are more and more common. (I understand that this is a controversial topic in its own light.) I can understand where they're coming from, and I'd be fine with a browser extension. Hopefully the one a Chrome developer is working on[1] will be available before this Chrome release hits stab…
Sadly implementing it as an extension is a security issue, as mentioned elsewhere plenty.
I seem to have read this as "that extension won't be a content script (i.e. require access to all websites, like the existing extension)" initially, but on second reading, that might not be the case (and might, in fact, not be possible at all with the current APIs). Not too happy about having to add that kind of extension unless it's released by some trusted publisher ...