Re:It is time to unlink the “Backspace” – Browser Back short...
by ubernostrum on Saturday August 20, 2016 @09:18PM
(#12329033)
If you want an infinitely-customizable web browser which has everything available in a config option you're free to write one; multiple high-quality open-source engines are available to build around.
Not every feature is good or widely-used, and removing the ones that fail, rather than trying to keep them around but configurable, is simply the right thing to do.
Re:It is time to unlink the “Backspace” – Browser Back short...
by another-dave on Sunday August 21, 2016 @05:18AM
(#12330104)
You say "removing ones that fail", but surely that's the point here — it only fails for users who don't know what's going on.
If I deliberately reenable backspace as 'Back in browser history', I've no right to complain if I lose web app state; and if I get burned often, I'll disable it again. If I use it without any problems, what's the lose on Google's side?
Re:It is time to unlink the “Backspace” – Browser Back short...
by random_rr on Sunday August 21, 2016 @09:40AM
(#12330879)
Exactly. Taking your thought a step farther... You can enable the shortcut yourself via extensions! That way, there's no loss in Google's side. :) they don't have to maintain an obsolete feature, and any problems are yours, not theirs. You seem to have made their point for them.
Less code base to cover. Less tests. That's a win for the secs. And you're free to install an extension to retrieve the behavior of you want. Sounds like everyone wins.
Re:It is time to unlink the “Backspace” – Browser Back short...
by another-dave on Sunday August 21, 2016 @01:34PM
(#12331791)
Well taking that further, you could say the same with all keyboard shortcuts & they have nothing to test :)
Well, I'm free to install extensions on my own personal computer but not everywhere that I use Chrome.
It's the lazy way.
You're right that it adds complexity. Every line of code contributes to complexity, and increases the number of places a bug could manifest. That's just the nature of software development.
Most software doesn't exist in a bubble of strictly-defined use cases. Software such as web browsers target a huge (potentially the broadest) range of users. Driving towards the lowest common denominator, as Google have been doing with Chrome by stripping configuration options over the years, doesn't result in a product people love to use. It produces software that performs adequately for the majority, and nothing more.
For features like "backspace to navigate back", throw them behind a flag. Make them default-disabled. Don't even worry about putting it in Preferences - tell power users who need it where they can find it (chrome://flags).