So I I am trying to style a custom wordpress theme, however the breakpoints I'm using are being applied at all screen sizes, literally just overwriting the styles I've already written. I have never had this problem before, and I have used this exact code on other, non-WordPress sites. In fact I literally copied it over from a site I made in Gatsby.
this is my _breakpoints.scss file
$breakpoints: (
"xs":0,
"sm":30rem,
"md":45rem,
"lg":60rem,
"xl":75rem,
);
#mixin xs {
#media (min-width: map-get($breakpoints, "xs")){
#content;
}
}
#mixin sm {
#media (min-width: map-get($breakpoints, "sm")){
#content;
}
}
#mixin md {
#media (min-width: map-get($breakpoints, "md")){
#content;
}
}
#mixin lg {
#media (min-width: map-get($breakpoints, "lg")){
#content;
}
}
#mixin xl {
#media (min-width: map-get($breakpoints, "xl")){
#content;
}
}
#mixin breakpoint($bp: 0) {
#media (min-width: $bp) {
#content;
}
}
and this is the element I am working on. the element should be hidden until the lg breakpoint (60rem/960px)
.hero-logo-container {
display: none;
#include lg {
display: block;
}
}
I did wonder was it something odd with flexbox, but like I said I've literally just used the exact same _breakpoints .scss on another site and it works fine. I have also thought that this may be some odd quirk of WordPress?
any help you can give me would be appreciated
I have tried hard-coding the file path to the image, in case that was the culprit (rather than using get_theme_file_uri()) but that wasn't it, other styles are just being similarly overridden.
I have recreated what has been built so far in basic HTML, with the same SCSS files and the problem is happening there.
I just can't see what I'm doing wrong...
Related
Is there any way to use
"breakpoint"
for sass within
"Prepros"
?
you can write your breakpoints in different file and can name that file as "_breakpoint.scss"
In your main app.scss you can call you dependent file with import function. So in your app.scss you would write :-
app.scss
#import "_breakpoint.scss";
now you can use breakpoint in this file which you have define in _breakpoint.scss file.
Hope its clear!!
Yes. Here's an example:
#mixin breakpoint($point) {
#if $point == xs {
#media (min-width: 420px) { #content; }
} #else if $point == sm {
#media (min-width: 640px) { #content; }
} #else if $point == md {
#media (min-width: 960px) { #content; }
}
}
...specifying as many as you want. And then using breakpoints is as easy as this:
.my-class {
color: red;
#include breakpoint(md) {
color: blue;
}
}
In this example .my-class colour will be red, unless the viewport is at least 960px wide, in which case .my-class colour will be blue.
I hope this helps.
I am creating an SCSS grid with specific problem - I would like to use one variable name, for instance $pad (for padding values), but that $pad variable would need to be different in different media breakpoints.
Variable value is first set through out mixins that dynamically create breakpoints and set $pad value within them.
// Default value
$pad: 0;
#mixin resolution($breakpointName, someOtherValues) {
#if ($breakpointName == 'mobile') {
#media (min-width: 320px) and (max-width: 520px) {
$pad: 20px;
#content;
}
}
#else {
#media (min-width: 521px) {
$pad: 30px;
#content;
}
}
}
When I start to write code, I would like to use it like this
#include resolution(mobile) {
.test {
padding: $pad;
}
}
Here is the problem. While using libsass (NPM gulp-sass), variable $pad is passed as I intended and it outputs following CSS
// THIS IS OK - gulp-sass
#media (min-width: 320px) and (max-width: 520px) {
.test {
padding: 20px;
}
}
But if I use latest Ruby SASS to compile CSS through NPM gulp-ruby-sass, it outputs only default value for $pad
// THIS IS WRONG - gulp-ruby-sass
#media (min-width: 320px) and (max-width: 520px) {
.test {
padding: 0;
}
}
Where is the problem here? Is it my idea or is it a bug in either libsass or ruby sass?
If my idea is the problem, is there a way to achieve what I wanted somehow?
Ruby Sass is correct. Your value should be 0.
LibSass has a tendency to behind in features and behavior. It is emulating the behavior of Sass 3.3, which freely has access to global variables from within mixins/functions. There isn't a way to do this that will work with both Sass 3.4 and LibSass. The syntax you need to use to be able to access global variables is not backwards compatible.
Either drop down to Sass 3.3 (and live with the deprecated warnings) or forget about being able to use LibSass.
Your mixin will need to look like this for Sass 3.4 to work as desired:
#mixin resolution($breakpointName) {
#if ($breakpointName == 'mobile') {
#media (min-width: 320px) and (max-width: 520px) {
$pad: 20px !global;
#content;
}
}
#else {
#media (min-width: 521px) {
$pad: 30px !global;
#content;
}
}
}
I have been designing with CSS for years, but I am only just now learning how to use SASS. This is very much a beginner question, so please bear with me.
The reason I started looking into SASS was because I wanted to develop a responsive web design, but was hoping there was a better way to do it than manually make different style sheets for every screen size.
I believe that in principle, a CSS preprossesor like SASS should help with this issue... but at the moment I don't understand how.
If I have a div with the id #squishable, and on large screens I want it to have a width of 1000 pixels, and on small screens a width of 100 pixels, but a red background in both cases, I think I would do something like this:
$color = red;
#squishable {
backgorundcolor: $color;
}
#media only screen
and (min-width : 321px) {
#squishable {
width:100px;
}
}
#media only screen
and (min-width : 1824px) {
#squishable {
width:1000px;
}
}
However, I'm not sure this approach is in much of an advantage over just using CSS. Maybe as an example, it's too simplistic. But, in any case, I don't see exactly what I would be doing differently with SASS to make it easier to code for a responsive web design. Is this all there is to it?
Can someone help me get over this conceptual hurdle and let me know how I take advantage of SASS to create elements that are responsive? Hopefully with a simple example similar to what I've got above?
You can absolutely improve your workflow further!
Using SASS #mixin, #include, #content and regular variables you can setup an environment where you create your media queries "inline", or inside of your regular selectors if you will.
This is my mixin for media queries:
(never mind the stupid variable names and placeholder breakpoints)
// Breakpoints
$mq-tiny: 5em;
$mq-small: 10em;
$mq-medium: 15em;
$mq-large: 20em;
$mq-huge: 25em;
$mq-crazy: 30em;
#mixin mq($size, $direction: min-width, $media-type: only all) {
#if $size == tiny { #media #{$media-type} and (#{$direction}: $mq-tiny) { #content; } }
#else if $size == small { #media #{$media-type} and (#{$direction}: $mq-small) { #content; } }
#else if $size == medium { #media #{$media-type} and (#{$direction}: $mq-medium) { #content; } }
#else if $size == large { #media #{$media-type} and (#{$direction}: $mq-large) { #content; } }
#else if $size == huge { #media #{$media-type} and (#{$direction}: $mq-huge) { #content; } }
#else if $size == crazy { #media #{$media-type} and (#{$direction}: $mq-crazy) { #content; } }
#else { #media #{$media-type} and (#{$direction}: $size) { #content; } }
}
And here's an example of how it can be used:
SCSS:
.selector {
width: 100px;
#include mq(large) {
width: 1000px;
}
}
CSS output:
.selector {
width: 100px
}
#media only all and (min-width: 20em) {
.selector {
width: 1000px
}
}
Take note that you don't need to use a variable name for the width. You can pass 1000px instead of large if you want to.
You may also have noticed the optional arguments in the #mixin; $direction and $media-type. These arguments default to min-width and only all respectively, but if you pass them through the #include they'll change for that specific element only.
Example with other arguments:
SCSS:
.selector {
#include mq(1000px, min-height) {
width: 100px;
}
}
CSS output:
#media only all and (min-height: 1000px) {
.selector {
width: 100px
}
}
Hope this helps!
Edit:
Here's a pen if you want to play around with it.
To increase maintainability of your code you can use variables to define media queries breakpoints:
// define breakpoints
$small-screen: 321px;
$large-screen: 1824px;
$small: "only screen and (min-width:"#{$small-screen}")";
$large: "only screen and (min-width:"#{$large-screen}")";
// and so on...
// now you can esely manipulate with your media breakpoints
#media #{$small} {
...
}
#media #{$large} {
...
}
Highly recommend you develop your SAAS css style import bootstrap framework, it will save you much time at responsive web designs
More detailed information please see this link:
http://pivotallabs.com/sass-with-bootstrap/
http://css-tricks.com/media-queries-sass-3-2-and-codekit/
I recently discovered this technique while reading about scss. I've come to enjoy writing lesscss and I would rather not switch. I was curious as to what options lesscss has to accomplishing a similar technique? I really like the idea of writing media queries inside the primary class/id declaration.
#mixin breakpoint($point) {
#if $point == papa-bear {
#media (max-width: 1600px) { #content; }
}
#else if $point == mama-bear {
#media (max-width: 1250px) { #content; }
}
#else if $point == baby-bear {
#media (max-width: 650px) { #content; }
}
}
.page-wrap {
width: 75%;
#include breakpoint(papa-bear) { width: 60%; }
#include breakpoint(mama-bear) { width: 80%; }
#include breakpoint(baby-bear) { width: 95%; }
}
UPDATE
I have found this answer http://blog.scur.pl/2012/06/variable-media-queries-less-css/ my only critism is how can I make it so that the media queries arnt redundant? how would I make this all compile into 1 mediaquery block?
This is how I do my media queries in LESS, utilising query bubbling as outlined in the article you linked to:
#palm : ~"screen and (max-width: 40em)";
#lap : ~"screen and (min-width: 50em)";
#desk : ~"screen and (min-width: 60em)";
.some-class {
color: red;
#media #lap {
color: blue;
}
}
Unfortunately though there is no way to have it all compile down to one media query block. This may also be the case with SASS/SCSS. The only reason this could be a problem is that is increases file size.
However you shouldn't worry about that. Why? The repetition of multiple media query blocks is negated by GZIP (more repetition == better compression). So providing your server is encoding with GZIP (most do, if not you should be able to enable it, it's worthwhile) you will not see any/much increase in file size.
Finally, even discounting GZIP, I still wouldn't want it to compile to one media query block. On any large CSS code base the proximity of having media queries next to the selectors is useful and desirable
I'm getting errors compiling my Sass files using media query mixins. I followed several tutorials, but it won't compile. I'm using Sass 3.3.0.alpha.67 (Bleeding Edge).
Here's my code
/* Included at the end */
#mixin mobile-only {
#media (max-width : 320px) {
#content;
}
}
/* Included where the rest of my sass is */
body { #include mobile-only {
display: none;
}
}
I'm using Scout to compile and watch for changes. Is there anything else I need to be doing?
Doesn't seem to be an issue anymore. The slightly modified code is explained in this codepen http://codepen.io/danielcgold/pen/RRNrPQ.
#mixin start-desktop-size {
#media (min-width: 1024px) {
#content;
}
}
body {
#include start-desktop-size {
background: red;
}
}