# Chrome Autocomplete **URL:** \ **Category:** Product Support\ **Created:** [February 12, 2019, 1:56pm UTC](https://meta.discourse.org/t/chrome-autocomplete/108953 "2019-02-12T13:56:52Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![thefreekick](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thefreekick/32/43228_2.png) [@thefreekick](https://meta.discourse.org/u/thefreekick)\ **Post date:** [February 12, 2019, 1:56pm UTC](https://meta.discourse.org/t/chrome-autocomplete/108953/1 "2019-02-12T13:56:52Z")
Is it possible that the changes made to turn autocomplete=off on the composer text area have broken predictive text input for users? Since upgrading last week I’ve had a number of users pointing out that predictive text no longer works for them on Android mobile via Chrome or stock browsers and using stock keyboard or other keyboards. It looks like this happened around the same time as [autocomplete was turned off in 2.2](https://meta.discourse.org/t/discourse-version-2-2/95438/5). I know this was done for another reason but just wondering if it could have caused this problem now or if it’s unrelated. This also appears to be happening on [try.discourse.org](http://try.discourse.org). I can’t verify myself without an Android device but one of my users tested it there and predictive text changes are no longer kicking in. ![image](https://global.discourse-cdn.com/meta/original/3X/f/0/f0b6521bae0232fb65b5bcc5dec80072dba48d4a.png) --- _[View the full topic](https://meta.discourse.org/t/chrome-autocomplete/108953)._