141–150 of 594 posts
Anyone want to place bets on how long till Firefox copies them?
When Firefox copies this "feature", at least there'll be an about:config option to disable it.
Earlier quoted context omitted.
Same thing with Firefox. It's really frustrating. The options are incredibly sparse. I feel like there is a complete lack of creativity on the part of browser developers are to features that it'd be nice to have
At least Firefox has about:config, and everything can be changed there.
I wanted to use Ctrl+N, Ctrl+O and Ctrl+T shortcuts in my webapp. I reported a bug 3 years ago https://bugs.chromium.org/p/chromium/issues/detail?id=321810 which is not fixed yet, but they have "fixed" Backspace ... that seems crazy to me.
Earlier quoted context omitted.
Ah, yes. On OS X, Ctrl+Q and Ctrl+W (well, their CMD equivalents) are system-wide and it drives me crazy if I hit Ctrl+Q by accident, or that devs prompt to quit because of how easy it is to accidentally press it instead of W. I'm so glad that tabs and state reload in pretty much every app I use these days...
On OS X, go to the Chrome menu, select "Warn Before Quitting". This makes it so you have to hold Cmd-Q to exit. No more accidental closing.
Earlier quoted context omitted.
Wait someone to implement it then extract source or implement it yourself, but rather than going through the store, add the code you inspected/wrote to the browser by enabling "Developer mode" in the Extensions (chrome://extensions/) then clicking "Load unpacked extension". This would be a very simple piece of code so getting no updates is actually better for security in this case IMHO.
Chrome now disables it unless it's in the app store: https://support.google.com/chrome/answer/2811969?hl=en EDIT: And prompts you to disable it at startup if it's unpacked.
Earlier quoted context omitted.
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.
Yeah, I remember doing it once and thinking it was extremely helpful at the time, but I only remember doing it once so far.
Chrome / 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 think some of those complaints reaching the front page of reddit may have helped spur this into action by the Chrome team.
This 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…
Is there any replacement for that Esc=STOP functionality? Every now and again I run into a site that will display some content, and then 1-2 seconds later, cover it up with a full-page ad or signup modal or whatever. I wish I could just refresh and hit "Esc" really quick, like the good old days.
After the smoke cleared, I came to the conclusion that Firefox had crossed a threshold and transformed from being a networked document display application to being an operating environment that was a platform for applications. Javascript, the DOM and CSS had advanced to the point where keyboard controls biased towards convenient document browsing no longer made sense.
I'd be all for Firefox removing the Backspace default keybinding even though it would slightly inconvenience me since that's the key I use to go back.
Earlier quoted context omitted.
When Firefox copies this "feature", at least there'll be an about:config option to disable it.
In Firefox, backspace has defaulted to "scroll up" for years now and yes, browser.backspace_action in about:config controls this.
It's been less than 36 hours since I lost several hundred words of work because of this, so I'm pretty sure the default behavior is "go back" as of the latest stable version (46.0.1).
