Text Assist Error 1.2.1
Javier
via web
Held out until I could replicate it before posting it here.
The Text Assist bug is still there in 1.2.1, but now it only happens after you've tapped outside of the text box. Anything that was typed before tapping out will not bug. I'll provide examples with 'swe' being corrected to 'she'.
Scenario 1:
'swe swe swe swe' is corrected to 'she she she she'.
I change it back to the original and send the tweet, never tapping outside the text box.
The correct tweet is posted.
Scenario 2:
'swe swe' is corrected to 'she she', and I change it back to the original.
Tapped outside the text box and tap into the text box again.
Add 'swe swe', which is corrected to 'she she', and I change it back to the original.
After sending the tweet, it appears as: 'swe swe she she'
Scenario 3:
Tap outside the text box before typing anything at all, and tapping into the text box again.
'swe swe swe swe' is corrected to 'she she she she', and I change it back to the original.
After sending the tweet, it appears as: 'she she she she'.
Hope this helps.
Support Staff 2 Posted by Moe on 18 May, 2011 08:19 AM
Javier first I wanna' thank you for taking the time and doing a detailed out test for us, it's highly appreciated.
It appears that it goes back to the original bug which is a webOS 2.1 bug with TextAssist. Previously we had the TextField disabled upon tapping Tweet which caused this bug, now that we changed that behavior and don't disable the TextField after tapping Tweet it looks like the bug is there everytime the TextField gets disabled or loses focus... I'll report this to the webOS team and see what they have for us as a feedback.
Thanks again for the detailed report.
3 Posted by kulf on 17 Jun, 2011 10:56 PM
Happens with German UI all the time.
Carbon will send out words that were deemed incorrect and autocorrected, yet changed back.
Look what this post looks like - it was subject to autocorrection as well...