-
Notifications
You must be signed in to change notification settings - Fork 13.4k
fix(datetime): allow calendar navigation in readonly mode; disallow keyboard navigation when disabled #28336
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
Conversation
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.
We spoke offline about using the toBeDisabled
assertion instead for many of these checks. This will let us consolidated tests and simplify the tests we end up keeping.
The implementation works well! I saw a few opportunities to clean up the code, but nothing major.
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.
I'm fine with the changes as-is, but I would like to make sure one of the changes was intentional.
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.
Thanks for sorting through everything here!
Co-authored-by: Amanda Johnston <90629384+amandaejohnston@users.noreply.github.com>
Issue number: #28121
What is the current behavior?
It is not possible to navigate between months when ion-datetime is in readonly mode. This means that if there are multiple dates selected, the user cannot browse to view them all.
Also, keyboard navigation is not prevented in
readonly
ordisabled
mode where it should be.What is the new behavior?
When
readonly
:When
disabled
:Known bug:
prefers-wheel
whendisabled
. This bug existed prior to this PR. I created FW-5408 to track this.Does this introduce a breaking change?
Other information