Normalize #153
Conversation
…iant... Also, customers who have only 1 variant may still want to show the variant title if it's not set to 'Default Title' so I am removing the condition altogether rather than fixing it.
…st 1 variant..." This reverts commit 3c68c5a.
@@ -733,10 +755,7 @@ h1, h2, h3, h4, h5, h6, | |||
h1 a, h2 a, h3 a, h4 a, h5 a, h6 a, | |||
.h1 a, .h2 a, .h3 a, .h4 a, .h5 a, .h6 a { font-weight: inherit; } |
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.
@mpiotrowicz Should I just extend h1 from .h1 (and so on), rather than duplicate up the selectors here and below?
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.
hmm, I'd probably go as follows:
h1,h2,h3,h4,h5,h6 {
a {
font-weight: inherit;
}
}
and then have all the typography helpers extend the tags, so
.h1 {
@extend h1;
}
That would include the link inside .h1 as well
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.
Am I the devil if I keep those extends on one line?
.h1 { @extend h1; }
.h2 { @extend h2; }
.h3 { @extend h3; }
.h4 { @extend h4; }
.h5 { @extend h5; }
.h6 { @extend h6; }
It goes against the styleguide, but it's so pretty.
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.
I'd stick with the guide for consistency. This style works but as soon as anything has to change, it would have to move to 2 lines anyway.
Add jQuery selectors to doc ready
Conflicts: assets/timber.scss.liquid
Normalize CSS and Clean shop.js
First stab at normalizing the CSS, rather than resetting.
normalize
code in to the sections where the rest of the attribute is definedResolves #151