Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Datepicker hint displayed on top of value on incorrect input #8575

Closed
robindijkhof opened this issue Nov 21, 2017 · 1 comment · Fixed by #8603
Closed

Datepicker hint displayed on top of value on incorrect input #8575

robindijkhof opened this issue Nov 21, 2017 · 1 comment · Fixed by #8603
Assignees
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@robindijkhof
Copy link
Contributor

robindijkhof commented Nov 21, 2017

Bug, feature request, or proposal:

Bug

What is the expected behavior?

The hint on the datapicker should be red(or something else) when an incorrect value is entered

What is the current behavior?

The hint on the datepicker is displayed on top of the value when an incorrect value is entered

What are the steps to reproduce?

Open the material datepicker examples : https://material.angular.io/components/datepicker/examples
Enter asd in the first datepicker
Lose focus

What is the use-case or motivation for changing an existing behavior?

The hint and the value are not readable anymore

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Material rc.1
Angular 5.0.2

Windows Chrome 62
Windows FireFox 57

Is there anything else we should know?

@crisbeto crisbeto self-assigned this Nov 22, 2017
@crisbeto crisbeto added has pr P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent labels Nov 22, 2017
crisbeto added a commit to crisbeto/material2 that referenced this issue Nov 22, 2017
…ped in

Fixes the datepicker input's placeholder not floating if the user types in an invalid value. This was due to the datepicker's value being parsed to `null` which the form field inferred as empty. These changes switch to always check the DOM element, rather than the actual control value.

Fixes angular#8575.
crisbeto added a commit to crisbeto/material2 that referenced this issue Nov 24, 2017
…ped in

Fixes the datepicker input's placeholder not floating if the user types in an invalid value. This was due to the datepicker's value being parsed to `null` which the form field inferred as empty. These changes switch to always check the DOM element, rather than the actual control value.

Fixes angular#8575.
tinayuangao pushed a commit that referenced this issue Dec 1, 2017
…ped in (#8603)

Fixes the datepicker input's placeholder not floating if the user types in an invalid value. This was due to the datepicker's value being parsed to `null` which the form field inferred as empty. These changes switch to always check the DOM element, rather than the actual control value.

Fixes #8575.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants