Currently it's only possible to toggle autocomplete on/off.
Setting it to off has even an invalid value in the frontend: autcomplete="off_82vmeLIU"
Since it's important for screenreaders and the browser builtin autocomplete functionality, I would recommend to implement the following features:
- adding a suffix to the "off" value becomes an invalid value -> fix off value
- implement mulitple text field components (regular text field, country text field, street text field) which inherently have already the correct autocomplete values
- use a single text field component where the user has the possibility to override this autocomplete value for complex use cases
3.1 display a select field with predefined given autocomplete values
3.2 display a text field where the user can use a custom autcomplete value
Reason:
- proper screenreader and browser detection of input fields
- WCAG2.2 accessibility rule: https://www.w3.org/TR/WCAG22/#identify-input-purpose
List of possible autocomplete values: https://www.w3.org/TR/WCAG22/#input-purposes
more from the HTML spec: https://html.spec.whatwg.org/#autofilling-form-controls:-the-autocomplete-attribute
Currently it's only possible to toggle autocomplete on/off.
Setting it to off has even an invalid value in the frontend:
autcomplete="off_82vmeLIU"Since it's important for screenreaders and the browser builtin autocomplete functionality, I would recommend to implement the following features:
3.1 display a select field with predefined given autocomplete values
3.2 display a text field where the user can use a custom autcomplete value
Reason:
List of possible autocomplete values: https://www.w3.org/TR/WCAG22/#input-purposes
more from the HTML spec: https://html.spec.whatwg.org/#autofilling-form-controls:-the-autocomplete-attribute