Skip to content
This repository has been archived by the owner on Nov 22, 2021. It is now read-only.

chrome autofill interaction #368

Closed
schwer opened this issue Feb 18, 2015 · 1 comment
Closed

chrome autofill interaction #368

schwer opened this issue Feb 18, 2015 · 1 comment
Labels
component: tags-input status: replied type: bug
Milestone
2.3.0

Comments

@schwer
Copy link

schwer commented Feb 18, 2015

Chrome autofill interacts poorly with the autocomplete widget. To see this behavior, you need to have autofill enabled in your desktop chrome browser, and using a field-name that chrome interprets as "fillable" like a street address or zipcode. And, you need to have something in your autofill settings. The consequence of this problem is a dropdown that appears above the autocomplete dropdown and prevents you from clicking on the first item amongst the autocomplete options.

I am using Chrome 40.0.2214.111. ngTagsInput v2.0.1. Angular 1.2.16.

A simple solution is to specify

<input autocomplete="off"'

in the tags-input.html template.
@mbenford
Copy link
Owner

Thanks for reporting this! I'll add it to the backlog.

@mbenford mbenford added this to the 2.3.0 milestone Mar 13, 2015
Bessonov pushed a commit to Bessonov/ngTagsInput.ie8 that referenced this issue May 3, 2015
@mbenford @Bessonov
fix(tagsInput): Ensure autocomplete attribute is off
4ce0d52 
Ensure the inner input's autocomplete attribute is set to 'off' so the
browser autofill system doesn't get activated.

Closes mbenford#368
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
component: tags-input status: replied type: bug
Projects
None yet
Milestone
2.3.0
Development

No branches or pull requests
2 participants
@mbenford @schwer