Hello Altitudes,

The input that you see when you post a new update is not really a "textarea" per-se. It's actually a HTML5 editable block (div) and we needed to use this as a work around because for suggestions to really work, this is necessary. There is no way to inject html codes into a plain textarea.

Apart from that, we also have the auto expanding functionality on the div itself so that it seems like the textarea would automatically expand as you type.

I believe the gestures and auto correction on your mobile device will most likely only work on textarea or text inputs.

Not sure I got what you said... From what you wrote I understand that you are not using textareas, but when I look at the HTML code I see:

<textarea class="es-story-textfield" name="content" autocomplete="off" data-story-textfield="" data-mentions-textarea="" data-default="" data-initial="0" placeholder="Share what's new..."></textarea>

And maybe the autocomplete="off" explains why word suggestion is not working (tested with Chrome on Android 4.3). The funny thing is that with Android stock browser it works

That is just a "shadow" because we are playing around with CSS to deceive your eyes It's still a textarea that is storing the input but when you type, you are actually typing on a content editable field

Well, I think I have to insist a bit

I tried removing the autocomplete="off" in the textareas (in components/com_easysocial/themes/wireframe/story/default.php) and guess what? It perfectly works now when you write a story (Chrome on Android).

Would you agree to make this change in ES everywhere it is needed (story, discussion etc.)?

Hm, I am not entirely sure why autocomplete=off would cause such an issue but this attribute needs to be there to avoid double auto completion on the editable area. Will need to re-look into this again.

Hello

As of ES 1.4.8, this has not been fixed... Have you had time to look into it?

Thanks

Hey Altitudes,

I haven't had the chance to test this yet. Does it have any other side effects after removing the autocomplete="off" on the textarea?

Hello

No, I could not find any side effect. In fact, autocomplete attribute is not supported in textarea tag (see http://www.w3schools.com/tags/tag_textarea.asp), it is only for input tag.

So removing it would make your code cleaner and avoid having the side effect we are talking of. I could find 7 textareas with autocomplete attribute set in Wireframe template (in status, comment, conversation...), and where the attribute should be removed.

Tell me what you think!

Noted, will remove this in the status update form

Well, it should be removed from the 7 textareas I mentioned in my previous message... Because the issue is not only with the status update form!

I will only place this fix in a single location and test this out before globally removing them. If nobody complaints about this on the next release, we'll remove them globally

OK, let's remain cautious and then we will see!

Thanks for understanding