Just because so many of you can not select things properly, it does not mean that Google is wrong. It would be *nice* if Chrome would change it to the dumb way it works in firefox, but there is absolutely nothing *wrong* with this. Period. Learn to use a Computer.
Firefox does something like this in the location bar as well. Try selecting a chunk of text from the middle of the current URL, and drag your cursor above or below the location bar.
@edwinmcdunlap selecting half the text in the address bar and moving your cursor up or down is "expected" behavior for a textbox (like the address bar). But not expected behavior for a textarea in the DOM.
I wonder what Safari does? (I.e., is it a Webkit thing?) Agree that the Firefox/IE behavior gives a better UX. (Also, have to add: "You're technically correct -- the best kind of correct.")
And I thought I was the only one upset about that...
JulioGreff 10 months ago
Shift+up all the way :D
nddrylliog 10 months ago
Just because so many of you can not select things properly, it does not mean that Google is wrong. It would be *nice* if Chrome would change it to the dumb way it works in firefox, but there is absolutely nothing *wrong* with this. Period. Learn to use a Computer.
alexandertrefz 10 months ago
Firefox does something like this in the location bar as well. Try selecting a chunk of text from the middle of the current URL, and drag your cursor above or below the location bar.
edwinmcdunlap 10 months ago
@edwinmcdunlap selecting half the text in the address bar and moving your cursor up or down is "expected" behavior for a textbox (like the address bar). But not expected behavior for a textarea in the DOM.
rockinthesixstring 10 months ago
I rage'd.
tsfreh 10 months ago
"Google is Wrong, Wrongity, wrong, wrong, wrong" I want that on a t-shirt.
RigasTelRuun 1 year ago 11
I wonder what Safari does? (I.e., is it a Webkit thing?) Agree that the Firefox/IE behavior gives a better UX. (Also, have to add: "You're technically correct -- the best kind of correct.")
daicon2k6 1 year ago
@daicon2k6 I just tested this in Safari 5.0.3 on Windows 7 x64 and I can confirm it behaves the same as Chrome. Must be a WebKit bug.
SaberUK1 1 year ago 3
Huge nuisance!
silverstategal 1 year ago
You're right. It is technically correct, but it is a nuisance to the user.
AmorousEyes 1 year ago 5