-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Bug(datepicker) month day selection cursor issue #4533
Comments
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
May 14, 2017
Adds the `pointer` cursor to the calendar toggle and date cells, indicating that they're clickable. Fixes angular#4533.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
May 14, 2017
* Adds the `pointer` cursor to the calendar toggle and date cells, indicating that they're clickable. * Sets the `default` cursor on the disable states, instead of the `text` cursor. Fixes angular#4533.
jelbourn
pushed a commit
that referenced
this issue
May 15, 2017
* Adds the `pointer` cursor to the calendar toggle and date cells, indicating that they're clickable. * Sets the `default` cursor on the disable states, instead of the `text` cursor. Fixes #4533.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What is the expected behavior?
When hovering over month day text mouse cursor to be "pointer", like in material 1.
What is the current behavior?
Mouse cursor is "text"
What are the steps to reproduce?
https://material.angular.io/components/component/datepicker go to examples and start selecting for dates and all month days cursor is "text" type.
What is the use-case or motivation for changing an existing behavior?
To be same like material 1.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Material 2.0.0-beta.5
Google Chrome 58
The text was updated successfully, but these errors were encountered: