3 ms·
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 backsp
by another-dave 10y ago
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?
- random_rr 10y agoExactly. 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.
- another-dave 10y agoWell 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.