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
{{ message }}
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.
Create an md-datepicker, nested inside an md-input-container, nested inside a form.
Assign a name property to md-datepicker ("releaseDate" and "expirationDate" in my case)
Have Chrome autofill enabled with autocomplete fields available (specifically "email" in my case)
What is the expected behavior?
Autofill should not try to populate a datepicker.
md-datepicker should have an attribute like md-input-autocomplete that should set the "autocomplete" attribute and value in the generated input tag.
An alternative could be to disable autocomplete behaviors entirely (not sure how).
What is the current behavior?
Chrome will suggest to autofill the md-input generated by the md-datepicker with an email (in my case, but this may vary).
What is the use-case or motivation for changing an existing behavior?
If a user wants to autofill other fields of the form, the datepicker will be populated with wrong data.
Which versions of AngularJS, Material, OS, and browsers are affected?
AngularJS: 1.7.9
AngularJS Material: 1.1.12
OS: Mac OS High Sierra 10.13.6
Browsers: Chrome
Is there anything else we should know? Stack Traces, Screenshots, etc.
Nothing relevant
The text was updated successfully, but these errors were encountered:
What value would you assign in this case? The autocomplete attribute doesn't have any date-related values other than birth dates.
Do you just want to set autocomplete="off"?
Splaktar
added
needs: demo
A CodePen demo or GitHub repository is needed to demonstrate the reproduction of the issue
needs: more info
The issue does not contain enough information for the team to determine if it is a real bug
needs: feedback
The issue creator or community need to respond to questions in this issue
and removed
needs: more info
The issue does not contain enough information for the team to determine if it is a real bug
labels
Feb 1, 2020
I found in my tests that autocomplete="off" doesn't work anymore.
The new (hacky) way is to set autocomplete="new-search".
I've asked to explicitly propagate the parameter on the compiled <input> just to be future proof, in the eventuality that autocomplete="new-search" stop working again with a future update.
Splaktar
removed
needs: feedback
The issue creator or community need to respond to questions in this issue
needs: demo
A CodePen demo or GitHub repository is needed to demonstrate the reproduction of the issue
labels
Feb 14, 2020
OK, I think that it would be reasonable to accept a PR to add a new md-datepicker-autocomplete API for doing this. We're mostly relying on the community to send PRs for enhancements at this time as we're focused on fixing high priority bugs/a11y issues/perf problems only.
Bug
Detailed Reproduction Steps:
md-datepicker
, nested inside anmd-input-container
, nested inside aform
.name
property tomd-datepicker
("releaseDate" and "expirationDate" in my case)What is the expected behavior?
Autofill should not try to populate a datepicker.
md-datepicker
should have an attribute likemd-input-autocomplete
that should set the "autocomplete" attribute and value in the generated input tag.An alternative could be to disable autocomplete behaviors entirely (not sure how).
What is the current behavior?
Chrome will suggest to autofill the
md-input
generated by themd-datepicker
with an email (in my case, but this may vary).What is the use-case or motivation for changing an existing behavior?
If a user wants to autofill other fields of the form, the datepicker will be populated with wrong data.
Which versions of AngularJS, Material, OS, and browsers are affected?
Is there anything else we should know? Stack Traces, Screenshots, etc.
Nothing relevant
The text was updated successfully, but these errors were encountered: