-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Correct calendar high contrast #6938
Conversation
… dates outside of the date boundary (minDate, maxDate) when DateRangeType.Week is used.
Divs were recently changes to buttons for accessibility and they inherited a button style for the font line height causing the text to shift downwards significantly inside the cells. Switching back to the old default.
…out of range dates when DateRangeType is Month
…e updated high contrast rest / hover / active pattern.
…ntrast rest / hover / active pattern.
…ive high contrast states for the current day and selected day.
… active high contrast states.
1) Update calendar 'Go to today' button to appear as a link in high contrast mode 2) Update calendar day week and month selection types to conform with the updated rest / hover / active high contrast pattern 3) Fix calendar day selection bug where day text wasn't visible in high contrast
1) Fix issue where 'Go to today' link was broken 2) Fix issue where high contrast month hover state borders were not rounded 3) Fix issue where text in high contrast was shifting location for month, week and Month/Year hover states
…the buttons inherit the font-size.
Hey @jhellesen it looks like your snapshot tests failed. Is changing "Go to today" to " Go to today" (an extra space in front) intentional? |
No, and it's fixed now. Thanks. |
Cool, thanks! It looks like the newest snapshot failure is due to the addition of |
Sorry - that was an intentional change. I've pushed out an update to the snapshot. |
|
||
if (goTodayEnabled && navigatedDayDate && selectedDate) { | ||
goTodayEnabled = | ||
navigatedDayDate.getFullYear() !== selectedDate.getFullYear() || navigatedDayDate.getMonth() !== selectedDate.getMonth(); |
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.
You probably meant to use "today" date rather than "selected" date.
Bug happens when you navigate to previous month, then select a day in the middle of the month, the go to today button gets disabled and it shouldn't
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.
related bug, you're using getMonth() but that doesn't cover what days are actually visible - if you select a visible day at the beginning or end of the range that's in the previous month, the button gets enabled again even if it can't do anything.
@jhellesen Hello! I see that this PR has been open for quite some time, do you have any plans on fixing the screener visual regressions so that this can be merged? Please let us know if we can answer any questions! |
These changes are actually intentional, not regressions. We had an existing bug for a while with the font inheritance being broken, so we actually need the changes to be approved. Our calendar designer doesn't have access to approve them- who do we need to talk to? |
@lorejoh12 Ben (@betrue-final-final) should be able to help you with those. |
🎉 Handy Links: |
Pull request checklist
$ npm run change
Existing calendar component has several issues in high contrast
Focus areas to test
Microsoft Reviewers: Open in CodeFlow