# Autocomplete in Vanadium

**URL:** https://meta.discourse.org/t/autocomplete-in-vanadium/294174
**Category:** Bug
**Created:** [February 5, 2024, 12:06pm UTC](https://meta.discourse.org/t/autocomplete-in-vanadium/294174 "2024-02-05T12:06:21Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![PeakProsperity](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@PeakProsperity](https://meta.discourse.org/u/PeakProsperity)
#### Post date: [February 5, 2024, 12:06pm UTC](https://meta.discourse.org/t/autocomplete-in-vanadium/294174/1 "2024-02-05T12:06:21Z")

</div>

I’ve received reports from our users that auto-complete does not work when using an Android phone with GrapheneOS and the Vanadium browser. I believe this is related to the following:

> [@Topic title and category filter autocomplete on Chrome](https://meta.discourse.org/t/topic-title-and-category-filter-autocomplete-on-chrome/195543):
>
> Related to [New post/reply sometimes tries to autocomplete my address on Chrome](https://meta.discourse.org/t/new-post-reply-sometimes-tries-to-autocomplete-my-address-on-chrome/107484). I’m using Chrome 91.0.4472.120 on Android 11 and it gives suggestions on some fields that clutter the UI, the topic title being the most common but it also happens on the category and tag filter fields: As a user I can long press and remove the suggestion, but most people on my community aren’t very tech savvy and I’d like to avoid this confu…

Can somebody tell me if there are any potential solutions to this? If not, can this be looked into? A number of our users are on De-Googled phones that use this browser. The browser is chrome-based and simply optimized for the GrapheneOS, so I’m surprised it would otherwise be much different.

Thanks in advance for any attention.