# Chrome Autocomplete

**URL:** <https://meta.discourse.org/t/chrome-autocomplete/108953>\
**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:** 4

<div class="post-metadata">

**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")

</div>

> [@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

---

_[View the full topic](https://meta.discourse.org/t/chrome-autocomplete/108953)._