Comment #116 on issue 26140 by [email protected]: Chrome Linux single click does not select all http://code.google.com/p/chromium/issues/detail?id=26140
When it comes to behaviour of the primary selection in relation to Chrome UI elements, my views are very simple: 1. Selecting something must populate the primary selection... no exceptions. No deviation from of expected behaviours has annoyed me more than when KDE 4 bugs caused this kind of thing. The primary selection is already minimally-discoverable. Don't confuse or frustrate people by breaking the expected behaviour of the only way to populate it from the omnibar. (In other words, people have been trained to expect selected=PRIMARY. Even something like "single-click = select, triple-click = PRIMARY" would be confusing at best since people tend not to read documentation.) 2. Middle-clicking a tab must close it. It's the expected behaviour, the close buttons are small and sometimes hidden, and tabs are more like buttons than text fields, so using a behaviour based on "paste" rather than "close" isn't only non- intuitive, but counter-intuitive. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
