bug: Cannot select a date in not-current month in ion-datetime on Android
See original GitHub issuePrerequisites
- I have read the Contributing Guidelines.
- I agree to follow the Code of Conduct.
- I have searched for existing issues that already report this problem, without success.
Ionic Framework Version
- v4.x
- v5.x
- v6.x
Current Behavior
In v6, when i click on one of the arrows in the top-right of the date-time component -or select a different month via the top-left option- I cannot select a date without it jumping to the previous month. If you then click a date, it goes back to the previous month again.
Tested in dev & production on real device and emulator with newest release candidate of the v6 beta.
Expected Behavior
Click on a date, that date gets selected
Steps to Reproduce
- Add a
<ion-datetime>
component to any screen. - Use capacitor to run the project on an Android phone or emulator.
- Try to select a date in a different month than the current one
Code Reproduction URL
https://github.com/Hugocaminada/datetime-test
Ionic Info
Require stack:
- /usr/local/lib/node_modules/@ionic/cli/lib/project/index.js
- /usr/local/lib/node_modules/@ionic/cli/lib/index.js
- /usr/local/lib/node_modules/@ionic/cli/index.js
- /usr/local/lib/node_modules/@ionic/cli/bin/ionic
Ionic:
Ionic CLI : 6.18.1 (/usr/local/lib/node_modules/@ionic/cli) Ionic Framework : @ionic/angular 6.0.0-rc.3 @angular-devkit/build-angular : 12.1.4 @angular-devkit/schematics : 12.2.13 @angular/cli : 12.1.4 @ionic/angular-toolkit : 4.0.0
Capacitor:
Capacitor CLI : 3.3.2 @capacitor/android : 3.3.2 @capacitor/core : 3.3.2 @capacitor/ios : not installed
Utility:
cordova-res : 0.15.3 native-run : 1.5.0
System:
NodeJS : v14.17.3 (/usr/local/bin/node) npm : 7.24.0 OS : macOS Monterey
Additional Information
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top GitHub Comments
This issue has been fixed in Chrome 97. It is slated to release Jan 4, 2022. I will keep this issue open until Chrome 97 ships. Thanks again!
Chrome 97 is releasing today which has a fix for this issue, so I am going to close this thread. Thanks for the report!