Help Swype erases first word on forum posts

[Deanie]

I just got my S4 last week, but I've been an android/droid user for a few years.

I use swype for the keyboard. And already I've noticed that when I type out text in the text block of a forum, the first word on a new line gets erased and a space inserted after I finish typing the word. Sometimes if I hit the space key after that first word it doesn't erase. I can't figure out what is happening.

I have auto capitalize and auto space enabled. I've used swype for years as well, and I've never seen this.

Has anyone seen this, or have a solution other than repeating the first word typing until it sticks? I don't know whether this is an issue in my handset, the swype application, or the forum itself.

FYI, I typed this post up using an ipad, so I had no issues.

Thanks for your help!

 

[Frisco]

Hello Deanie.

We've seen this and other similar issues reported around the forums. Are you using the stock swype or did you download the beta version?

Have you tried clearing cache and data in your keyboard/swype apps then rebooting?

 

[Deanie]

Hi Frisco.

I just did a bit more testing with the Samsung kb and swype, and it occurred with both.

Then I decided to change browsers. I was using Chrome. So I switched back to the stock browser and the issue did NOT occur.

So my preliminary tests indicate a browser issue.

On previous devices I used Opera browser, not Chrome, so I think I will go back to that.

 

[SebaKL]

Hi Frisco.

I just did a bit more testing with the Samsung kb and swype, and it occurred with both.

Then I decided to change browsers. I was using Chrome. So I switched back to the stock browser and the issue did NOT occur.

So my preliminary tests indicate a browser issue.

On previous devices I used Opera browser, not Chrome, so I think I will go back to that.

You are not alone. Whenever I would sign with my disqus account to leave a comment, it was a horror to type. The pointer would jump lines, start deleting words in different paragraphs randomly. Specifically swype with chrome.

I eventually moved to swiftkey, while the swipe is not as forgiving, the predictions are unbelievable. Most of the time it takes just one letter to get the next predicted word right.

You may also try the native google keyboard. It's free and 4.2 compatible. Swipe works great, but the prediction isn't as good as on swiftkey.
And as much as I would love to use google key, I couldn't stand the lack of comma, given I use more commas than full stops, wasn't very practice. No doubt it will improve. You should give it a try, no harm keeping spare keyboard on standby

Google keyboard