We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Several modern browsers (Firefox, IE, Safari) do not natively support the date input. Does (or will) Material2 provide the needed shims for this?
date
date inputs should consistently render across browsers.
date input doesn't render into anything meaningful on non-Chrome browsers (below: Firefox)
<md-input type="date"></md-input>
http://plnkr.co/edit/nL8iy9hJ2usy8sfPOZsN?p=preview
As a UI framework, I think it's appropriate to say that Material is responsible for ensuring consistent component behavior across browsers.
I think all versions, but definitely v2.0.0-alpha.7-4, and the latest (v2.0.0-alpha.8-2)
v2.0.0-alpha.7-4
v2.0.0-alpha.8-2
The text was updated successfully, but these errors were encountered:
Duplicate of #675
They'll add it for sure in the future.
Sorry, something went wrong.
Yep, follow #675 for the full datepicker component.
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.
No branches or pull requests
Bug, feature request, or proposal:
Several modern browsers (Firefox, IE, Safari) do not natively support the
date
input.Does (or will) Material2 provide the needed shims for this?
What is the expected behavior?
date
inputs should consistently render across browsers.What is the current behavior?
date
input doesn't render into anything meaningful on non-Chrome browsers (below: Firefox)What are the steps to reproduce?
http://plnkr.co/edit/nL8iy9hJ2usy8sfPOZsN?p=preview
What is the use-case or motivation for changing an existing behavior?
As a UI framework, I think it's appropriate to say that Material is responsible for ensuring consistent component behavior across browsers.
Which versions of Angular, Material, OS, browsers are affected?
I think all versions, but definitely
v2.0.0-alpha.7-4
, and the latest (v2.0.0-alpha.8-2
)Is there anything else we should know?
The text was updated successfully, but these errors were encountered: