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
This repository's issues are reserved for feature requests and bug reports.
Do you want to request a feature or report a bug?
bug
Bug Report
On the docs home page, the four cards which link to pages show a text highlight cursor instead of a pointer. This makes it unclear that these cards can be clicked.
Screenshots or link to CodePen/Plunker/JSfiddle
What is the expected behavior?
Mouse should change to pointer cursor when hovering over cards that are links. It would also be nice if chrome understood it as a link too and showed the url at the bottom (similar to button links).
What is the motivation / use case for changing the behavior?
It is unclear that these are links until they are clicked on
Which version of Angular and Material, and which browser and OS does this issue affect?
Chrome
Did this work in previous versions of Angular / Material?
Please also test with the latest stable and snapshot versions.
N/A
Other information
(e.g. detailed explanation, stacktraces, related issues, suggestions how to fix)
The text was updated successfully, but these errors were encountered:
This repository's issues are reserved for feature requests and bug reports.
Do you want to request a feature or report a bug?
bug
Bug Report
On the docs home page, the four cards which link to pages show a text highlight cursor instead of a pointer. This makes it unclear that these cards can be clicked.
Screenshots or link to CodePen/Plunker/JSfiddle
What is the expected behavior?
Mouse should change to pointer cursor when hovering over cards that are links. It would also be nice if chrome understood it as a link too and showed the url at the bottom (similar to button links).
What is the motivation / use case for changing the behavior?
It is unclear that these are links until they are clicked on
Which version of Angular and Material, and which browser and OS does this issue affect?
Chrome
Did this work in previous versions of Angular / Material?
Please also test with the latest stable and snapshot versions.
N/A
Other information
(e.g. detailed explanation, stacktraces, related issues, suggestions how to fix)
The text was updated successfully, but these errors were encountered: