You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a fix, which is to change "off" to any other string (like "none" or "false", or "disabled"). Since we will have to change every single form, I propose we create a directive bhFormDefaults that attaches the autocomplete, autocapitalize, etc, attributes to the form element, instead of doing it manually. That way, if the chrome team changes its mind again, we only have to change one file, the bhFormDefaults file.
Like this:
<formname=" SomeForm" bh-form-defaults>
@IMA-WorldHealth/local-contributors what do you think?
The text was updated successfully, but these errors were encountered:
This commit adds a new directive `bhFormDefaults` to automatically add
attributes to any form element. These attributes are:
1. `autocomplete`
2. `autocapitalize`
3. `autocorrect`
The directive turns them off by setting them to "none". If a browser
updates in the future to ignore the "none" directive, they can easily be
updated.
Closes#502.
This commit adds a new directive `bhFormDefaults` to automatically add
attributes to any form element. These attributes are:
1. `autocomplete`
2. `autocapitalize`
3. `autocorrect`
The directive turns them off by setting them to "none". If a browser
updates in the future to ignore the "none" directive, they can easily be
updated.
Closes#502.
This commit adds a new directive `bhFormDefaults` to automatically add
attributes to any form element. These attributes are:
1. `autocomplete`
2. `autocapitalize`
3. `autocorrect`
The directive turns them off by setting them to "none". If a browser
updates in the future to ignore the "none" directive, they can easily be
updated.
Closes#502.
Previously, @lomamech did a lot of good work to ensure our forms behave properly, using
autocomplete="off"
,autocapitalize="off"
, and so on. In a recent bug repot chrome has stopped respecting the "off" attribute for autocomplete.There is a fix, which is to change "off" to any other string (like "none" or "false", or "disabled"). Since we will have to change every single form, I propose we create a directive
bhFormDefaults
that attaches theautocomplete
,autocapitalize
, etc, attributes to the form element, instead of doing it manually. That way, if the chrome team changes its mind again, we only have to change one file, thebhFormDefaults
file.Like this:
@IMA-WorldHealth/local-contributors what do you think?
The text was updated successfully, but these errors were encountered: