Skip to main content

Search and Top Navigation

#11050 closed bug (worksforme)

Opened February 09, 2015 10:31AM UTC

Closed February 09, 2015 02:47PM UTC

Chrome on android 4.4.2 - autocompletes when any key is pressed and is impossible to turn off

Reported by: joel mitchell Owned by: joel mitchell
Priority: minor Milestone: none
Component: ui.autocomplete Version: 1.11.2
Keywords: Cc:
Blocked by: Blocking:

Hello - this is a niche but annoying thing:

Chrome for Android 4.4.2 has it's own autosuggest that inserts words into the autosuggest field as soon as a key is pressed. This word then caches until the browser is closed and a different word is entered. I have autocomplete=off on the field but it seems uninterested....

Can you think of a fix to prevent this happening?

Best regards


Attachments (0)
Change History (3)

Changed February 09, 2015 01:30PM UTC by arschmitz comment:1

owner: → joel mitchell
status: newpending

Hi can you give a little more description how to reproduce this, and exactly what your seeing? Im trying to use on an Galaxy S5, with chrome for android, on android 4.4.2. Im not seeing the sort of behavior your describing, but i'm not certain i'm following the proper steps, to reproduce. Could you modify the jsbin, and include steps to reproduce please?

Changed February 09, 2015 02:22PM UTC by joel mitchell comment:2

status: pendingnew

Hmmm - it seems to not be a problem any more; guessing it got fixed with a Chrome build as this was very well tested the other day. Well that is both annoying and excellent, thank you for looking into this.

I think that this can be closed as I can't reproduce this on my local machine, the jQuery site or on my staging server.

Changed February 09, 2015 02:47PM UTC by arschmitz comment:3

resolution: → worksforme
status: newclosed

Thanks for the update. I'm going to close this, since you can no longer reproduce.