-
Notifications
You must be signed in to change notification settings - Fork 171
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
Increase contrast of switch track and thumb #5484
Conversation
As far as I understand the source issue #5470 , there are also some changes that need to be made to the figma library, that are not in scope of this PR. |
@jmuzina almost there! Can we please make the thumb border the same high contrast grey, for consistency? ATM, in the on state, it is blue and overlaps the border of the track, the two should match: |
The high contrast border color has some transparency, and is drawn over areas with different background colors so it appears differently over the track vs the thumb: ![]() ![]() Is this an expected result? Otherwise, we could flatten the high contrast border color. |
Explored two possible directions for the switch to go with @lyubomir-popov
![]()
![]() |
Discussed with @lyubomir-popov and Diana: We will go for option 2 above. I'll update this PR accordingly |
@lyubomir-popov I've updated the PR per our recent discussions. I also flattened the high contrast border color to get rid of the very slight discoloration visible in the "off" state when the high contrast border color has transparency: This color settings change also effects other components that use the high contrast border. Have a look at the visual regression test and let me know if anything unexpected has changed. |
Diana has some questions about potential improvements to the focus state. These will be discussed during visual office hours on Monday. |
@jmuzina I've approved the percy build, nothing looks out of place to me. |
Done
Fixes #5470 , WD-19209
QA
Check if PR is ready for release
If this PR contains Vanilla SCSS or macro code changes, it should contain the following changes to make sure it's ready for the release:
Feature 🎁
,Breaking Change 💣
,Bug 🐛
,Documentation 📝
,Maintenance 🔨
.package.json
should be updated relative to the most recent release, following semver conventionScreenshots