# Chrome Autocomplete **URL:** https://meta.discourse.org/t/chrome-autocomplete/108953 **Category:** 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:** 5 **Page:** 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) ---
### Author: ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot) #### Post date: [February 12, 2019, 5:35pm UTC](https://meta.discourse.org/t/chrome-autocomplete/108953/2 "2019-02-12T17:35:40Z")
I wouldn’t expect `autocomplete="off"` to interfere with predictive text, but I suppose it’s possible… I just tried in iOS and Android and autocomplete works as expected (i.e., I type `yhis` and it corrects to `this` automatically). Predictive suggestions still appear normally above my keyboard. Is it only the T9 style predictive input that’s broken (as per the screenshot)? ---
### Author: ![bletch](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bletch/32/69088_2.png) [@bletch](https://meta.discourse.org/u/bletch) #### Post date: [February 12, 2019, 6:17pm UTC](https://meta.discourse.org/t/chrome-autocomplete/108953/3 "2019-02-12T18:17:25Z")
I can’t add any detail here (happy to research it if needed) but I had a user report this too. I rather glibly told him that Discourse wouldn’t impact his Android keyboard behaviour but now I see another report I’m wondering if there’s something in it. Let me know if you need more details. ---
### 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, 6:22pm UTC](https://meta.discourse.org/t/chrome-autocomplete/108953/4 "2019-02-12T18:22:51Z")
> [@awesomerobot](#): > > Is it only the T9 style predictive input that’s broken (as per the screenshot)? I didn’t even know people still used T9 but yes it appears to be those T9 predictions that aren’t working in the composer for some people. It seemed to happen around my upgrade to 2.2 ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [March 4, 2022, 7:37am UTC](https://meta.discourse.org/t/chrome-autocomplete/108953/5 "2022-03-04T07:37:40Z")