-
Notifications
You must be signed in to change notification settings - Fork 2.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] Refactor button gradients #1392
Conversation
d7b8535
to
b6d21c4
Compare
Refactor button gradientsPreview: documentation |
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.
box-shadow: $button-intent-box-shadow; | ||
background-color: $hover-color; | ||
background-image: $button-intent-gradient; |
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.
do you need to repeat same background-image
in pseudo states like :hover
(compare to line 165)?
in devtools, it seems safe to remove.
this comment applies several times throughout the changed files, i'm just gonna leave this one comment for them all.
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.
Yeah, looks fine
Remove unnecessary background-image on hoverPreview: documentation |
I'm not sure about the new flatter buttons. Any chance we can reproduce the old gradient style? |
@pkwi that's just a refactor, not a change. Buttons didn't get flatter :) Edit: just realizing that default buttons used to have a different gradient than default button hovered... On it with Piotr offline for a clarification |
With 70% opacity for Seems pretty legit, gonna push a commit now and wait for @pkwi confirmation tomorrow. |
70% gradient opacity for default light buttonPreview: documentation |
Bump default gradient to 80%Preview: documentation | table |
80% looks good to me. |
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 is awesome
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.
Everything affected in the refactor seems good to me. what about gradients in menus, text inputs, etc? Any plan there?
menus and inputs don't have |
A bit late to the party, but perhaps the |
We name our sass variables for their type: |
Right, that is a good point! I overlooked that there was also |
Follow up from #1367
Changes proposed in this pull request:
linear-gradient-with-fallback
mixin and rely on straight CSS!default
variables that can be customized like all the other ones