-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Button] New design language #2746
Conversation
@@ -235,13 +236,16 @@ | |||
} | |||
|
|||
&:focus { | |||
box-shadow: 0 0 0 border-width('thick') var(--p-border-secondary); | |||
@include no-focus-ring; | |||
box-shadow: 0 0 0 border-width('base') var(--p-border-secondary); |
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.
This was probably out of date and changed in figma, or an oversight. This is the proper border width
d0569c5
to
01c7321
Compare
Does this include the |
Pressed states: https://screenshot.click/screencast_2020-02-18_09-32-32.mp4 Monochrome is very subtle in figma as well. Maybe we can do better there |
c13be7e
to
1a2c1e5
Compare
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.
A bunch of these updates to color variants are wrong. Be sure to check the latest variants here: https://github.com/Shopify/polaris-tokens/blob/76f897fb186b1976b762c9189f95d05f526ad328/src/configs/base.ts#L197.
In particular the interactive changes are wrong, and should be reverted. Not sure about the rest, but it would be worth giving these a good look through.
So weird, those colors weren't working locally for me. I think I may have to clear my yarn cache |
1a2c1e5
to
3ef6a0a
Compare
3ef6a0a
to
aa23d0b
Compare
} | ||
|
||
&:active { | ||
box-shadow: 0 0 0 border-width('base') var(--p-border-secondary); | ||
background: var(--p-surface-pressed); | ||
&::after { | ||
box-shadow: none; |
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.
Just a thought... we end up overwriting things about the ring in a few places. It doesn't feel right because it's so far detached for the source. If we change the ring, this will just add tech debt because chances are it will be left behind. Adding more arguments to the focus-ring with defaults would allow us to keep all the focus ring CSS in 1 location.
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.
Good point! I've been chatting with Alex about refactoring button css once the design language has been rolled out. I think that would be a good time to address things like this as we'll have a better idea of how the focus ring needs to be used
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.
🎩 looks good 🚢
This PR is meant to be the final push from partially completed in React to full
https://github.com/Shopify/polaris-ux/issues/371
I'd add some screenshots but I feel that would be ineffective. The best way to 🎩is to 🎩
WHAT is this pull request doing?
How to 🎩
🖥 Local development instructions
🗒 General tophatting guidelines
📄 Changelog guidelines
Copy-paste this code in
playground/Playground.tsx
:🎩 checklist
README.md
with documentation changes