Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

An unfortunate trend.

Chrome / Chromium have introduced a few non-optional changes recently that seem to have been implemented by North Americans / native English speakers / ex-or-current Microsoft windows users. Any or all of which are annoying for non-North Americans or people that don't use Microsoft Windows.

Two that spring to mind - clicking in the URL bar now selects the entire contents. It now has the dubious honour of being the only text entry box in any GNU/Linux application to work that way.

Similarly, dragging the scrollbar now has a snap-back feature if you move the mouse more than about 40px from the scrollbar 'region'. Again, the only application on any GNU/Linux DE that abuses the scrollbar in this fashion.

Requests by non-MS-Windows users to make these configurable settings, and/or respect OS defaults, are met with disdain.



Both issues are valid. Have you tried filing a bug? It's interesting that Google doesn't put a high priority on Linux boxes even though both of their operating systems (ChromeBook and Androids) are based on Linux kernel


Bugs exist, and are well populated (though I suspect many disgruntled users don't manage to track these things down to the code.google tracker).

The bug threads contain a predictable mix of well-reasoned, thoughtful explanations of the problem, polite requests for fixes, impolite and exasperated complaints, and developer responses ranging from 'you're wrong to want the earlier / native OS behaviour' to 'we won't fix it, for reasons'.

Snap-back bug 377191 [1] morphed into 377919 [2]. I'm pretty sure the non-intuitive 'snapback' name is an unfortunate and doubtless unintended example of making it harder for users to find, and report their preferences.

Looking at those two bug reports, there's at least another half dozen issue #'s that have been merged into these.

MS-Windows-like single-click to select the URL (rather than using the mouse as a pointer to position the cursor, as GNU/Linux users seem to be familiar with) bug reports date back a long time [3] with hints that not all the developers agree with the behaviour change (or the refusal to make it an option). Again, it's the kind of thing that people continue to identify and complain about elsewhere, for example on the Google product forums [4].

Just as with this one-time-offer-only, auto-translate pop-up bug -- I really dislike the allegedly modern behaviour of reducing configuration options inside software, while your shipped configuration annoys an ever-increasing section of your user base.

The alleged benefit of satisfying the handful of people who are easily bewildered by Settings dialogs is simply perverse.

</rant>

[1] https://code.google.com/p/chromium/issues/detail?id=377191

[2] https://code.google.com/p/chromium/issues/detail?id=337919

[3] https://code.google.com/p/chromium/issues/detail?id=26140

[4] https://productforums.google.com/forum/#!topic/chrome/AZt9L9...




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: