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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSS polish #85
CSS polish #85
Conversation
* <div class="sk-double-bounce1"></div> | ||
* <div class="sk-double-bounce2"></div> | ||
* <div class="sk-child sk-double-bounce1"></div> | ||
* <div class="sk-child sk-double-bounce2"></div> |
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.
@jmagnusson Adding specific classes for shared styles here, instead of relying on for example div
, 馃憤 / 馃憥 ?
I think your CSS/HTML skills severly out-whey mine. So do it 馃槈 |
@@ -13,12 +13,11 @@ | |||
&.sk-spinner { |
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.
@jmagnusson We use this pattern throughout SpinKit, but I'm considering if we should just kill this selector and make these styles part of the parent selector. E.g. making this:
.sk-spinner-double-bounce {
[styles]
}
鈥ather than:
.sk-spinner-double-bounce {
&.sk-spinner {
[styles]
}
}
Thoughts? 鉂わ笍
@jmagnusson Feeling done, mind trying this out before I merge? 馃憖 鉂わ笍 |
Lodash `template` function had a change in syntax so modified gulpfile.js to reflect this.
Had to update the dev dependencies to be able to run gulp. But everything seems just fine 馃憤 |
Nothing should really change because of this, purely implementation details.
cc @jmagnusson 馃憖