-
Notifications
You must be signed in to change notification settings - Fork 3.4k
fix(datepicker): Fix validation in IE. #10520
Conversation
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
Hey @topherfangio, Looks good to me, I've just noticed that Google Bot has put a message on this to get confirmation. I couldn't get the test runner to work in the end, but that was down to my old development machine. |
@richardhughes Thanks! I've marked it as |
@topherfangio - can you squash your commits. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM other than commits needing to be squashed and fixed to conform to commit rules.
Closing this in favor of #11110 since the request to squash commits was not resolved. |
## PR Checklist Please check that your PR fulfills the following requirements: - [x] The commit message follows [our guidelines](https://github.com/angular/material/blob/master/.github/CONTRIBUTING.md#-commit-message-format) - [x] Tests for the changes have been added (for bug fixes / features) - [x] Docs have been added / updated (for bug fixes / features) ## PR Type What kind of change does this PR introduce? ``` [x] Bugfix [ ] Feature [ ] Code style update (formatting, local variables) [ ] Refactoring (no functional changes, no api changes) [ ] Build related changes [ ] CI related changes [ ] Documentation content changes [ ] Infrastructure changes [ ] Other... Please describe: ``` ## What is the current behavior? this fixes a regression introduced in v1.1.0 against IE however the test is able to reproduce the issue on Chrome Issue Number: Fixes #9994. Closes #10520. Relates to #10015. ## What is the new behavior? The test passes and datepicker validation and ngMessages work properly on IE. ## Does this PR introduce a breaking change? ``` [ ] Yes [x] No ``` ## Other information thank you to Topher Fangio and Richard Hughes for the original solution
Adds in validation for the input as a last check as IE interpreted the date '11/14/2016d' as valid which is incorrect.
Note: This PR supersedes #10015 by adding a test.
Fixes #9994. Closes #10015.