-
Notifications
You must be signed in to change notification settings - Fork 0
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
Make use of currentColor #62
Conversation
@@ -3,10 +3,10 @@ | |||
// Easily pump out default styles, as well as :hover, :focus, :active, | |||
// and disabled options for all buttons | |||
|
|||
@mixin button-variant-plain($color, $background, $border) { |
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.
The $border
seemed to always be the same as $color
so I've removed and used currentColor
for all instances of both $color
and $border
except for the base rule color: $color;
which will get overridden by customer branding if needed
Do you think there's anything we can do with https://github.com/talis/rl-app/blob/master/src/classes/api/BrandingAPI.class.php to dump out the two core customer colours in the following format? Your instances of <style>
:root {
--customerPrimary: #101;
--customSecondary: #999;
}
</style> |
I don't see why not! Might we also need the navbar colour? I'm not sure what the plan is for focus on that... |
Ah, blummin' heck. Yes, that would be another property we'd need. Focus/active state-wise, the outline should be left at our be our default white state for now. |
Raised a PR: https://github.com/talis/rl-app/pull/2808 |
@@ -96,8 +96,8 @@ a.btn { | |||
|
|||
// Make a button look and behave like a link | |||
.btn-link { | |||
font-weight: 400; |
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.
Redefined two lines below
color: $link-color; | ||
border-color: transparent; |
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.
.btn-alert { | ||
text-decoration: none; | ||
&:hover { | ||
color: $white !important; | ||
} | ||
} |
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.
@@ -199,6 +199,10 @@ | |||
background-image: none; | |||
} | |||
|
|||
&:hover:active { | |||
background-color: $black; |
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.
Should favour hover background-color
when both hover
and active
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.
Was it going transparent again when clicked?
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.
Having experimented with CSS variables a little, they really don't play nicely with SCSS... as soon as you want to pass the variable to a function, the sass compiler errors with messages along the lines of |
That's OK. A custom property could be modified with a built-in CSS function instead. We'd modify the |
dist/app.css
Outdated
@@ -226,7 +226,7 @@ a { | |||
text-decoration: 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.
Don't worry about commiting changes in app.css
: there's a task to generate the dist files when the version is bumped.
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.
Oh yeah… the release process. I've been using conventional-commits to help with this. Would you agree that this commit is probably of 'fix', so will bump the patch version?
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.
Yep, agree
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.
Happy with how it's rendering on http://localhost:8000/ ?
To allow customer branding to cascade
Co-authored-by: Dan Matthew <dm@talis.com>
da0a006
to
711d8df
Compare
To allow customer branding to cascade
Also includes some miscellaneous fixes picked up from reviewing the update with customer branding in Shipshape