Comment 2 by jteh on 2011-06-19 22:56
Most likely caused by 36c938c (fix for #1566). We'll probably have to revert this and thus cause #1566 again.
Changes:
Milestone changed from None to 2011.2

Comment 3 by mdcurran on 2011-06-19 23:33
Nope, not caused by that. Has existed most likely since 2a3e558.
I'm very tempted to take that code out (the code that does that expand to word, expand to textEdit, is it before the start) if so expand to textEdit and collapse. It was added to fix some weird issue when at the end of some edit fields... but I can't reproduce that problem, and all that code has changed majorly since. It also speeds things up some what if its taken out.
Note that its also currently sometimes causing other content outside the edit field to be read when moving by line in some textAreas.

Comment 4 by briang1 on 2011-06-20 12:07
I had this problem today when updating some tickets. Yes, also the reading bits outside the edit area also happened as well. Bit flakey. Maybe you should remove the code and give it some extended testing .

Comment 5 by mdcurran on 2011-06-21 10:04
Fixed in c94b81d. However, there is a possibility this could bring back another bug (not ticketed it seems) to do with the caret when at the end of an edit field it seems as though its before the start. 2a3e558
Changes:
State: closed

Comment 6 by jteh on 2011-06-28 05:57
I think he meant fixed in d17563f. :)