bug(Autocomplete): Browser Autocomplete conflicting with custom autocomplete

[svengraziani]

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Reproduction

Steps to reproduce:

1. Any anglify-autocomplete component
2. ensure you submitted that form so that the browser can store the value for the next time, suggesting it's own autocomplete.

Expected Behavior

Possibility to disable browser autocomplete to ensure only the custom autocomplete is used.

Actual Behavior

Browser autocomplete and custom autocomplete show up. But if the browser autocomplete field is selected, no valid value gets written to the field. Leading to a filled field, which has the same option "at least as seen by the user" but has no selection.

Environment

• Angular: 14.2.8
• Anglify: 0.39.0
• Browser(s): Google Chrome 107.0.5304.87 (arm64)
• Operating System (e.g. Windows, macOS, Ubuntu): macOS Ventura 13.0

[valentingavran]

At the moment we have set internally the following attribute on the input fields [autocomplete]="false". This is not correct. It should be autocomplete="off".

We should also give the developer the possibility to configure this himself via an input property.