cascade option in gulp-autoprefixer
While adding the autoprfixing task from the gulp-autoprefixer plugin I noticed the
autoprefixer({ cascade: false })
option. And this option was not clear for me what it is doing.
In the documentation I read that:
cascade (boolean): should Autoprefixer use Visual Cascade, if CSS is uncompressed. Default: true
So I compiled my SASS to the CSS with the cascade: false and with cascade true and I got the same result in both cases:
My SASS:
body
display: flex
p
display: flex
Compiled to the CSS with the autoprefixer({ cascade: false }):
body {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
body p {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
Compiled to the CSS with the autoprefixer({ cascade: true }):
body {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
body p {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
So my final question is - What the autoprefixer's cascade: false/true option is responsible for?
Thank you very much for the answer.
css gulp gulp-sass gulp-autoprefixer
asked Nov 20 '18 at 14:31
Wiktor KrólWiktor Król
62
add a comment |
While adding the autoprfixing task from the gulp-autoprefixer plugin I noticed the
autoprefixer({ cascade: false })
option. And this option was not clear for me what it is doing.
In the documentation I read that:
cascade (boolean): should Autoprefixer use Visual Cascade, if CSS is uncompressed. Default: true
So I compiled my SASS to the CSS with the cascade: false and with cascade true and I got the same result in both cases:
My SASS:
body
display: flex
p
display: flex
Compiled to the CSS with the autoprefixer({ cascade: false }):
body {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
body p {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
Compiled to the CSS with the autoprefixer({ cascade: true }):
body {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
body p {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
So my final question is - What the autoprefixer's cascade: false/true option is responsible for?
Thank you very much for the answer.
css gulp gulp-sass gulp-autoprefixer
asked Nov 20 '18 at 14:31
Wiktor KrólWiktor Król
62
add a comment |
While adding the autoprfixing task from the gulp-autoprefixer plugin I noticed the
autoprefixer({ cascade: false })
option. And this option was not clear for me what it is doing.
In the documentation I read that:
cascade (boolean): should Autoprefixer use Visual Cascade, if CSS is uncompressed. Default: true
So I compiled my SASS to the CSS with the cascade: false and with cascade true and I got the same result in both cases:
My SASS:
body
display: flex
p
display: flex
Compiled to the CSS with the autoprefixer({ cascade: false }):
body {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
body p {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
Compiled to the CSS with the autoprefixer({ cascade: true }):
body {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
body p {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
So my final question is - What the autoprefixer's cascade: false/true option is responsible for?
Thank you very much for the answer.
css gulp gulp-sass gulp-autoprefixer
asked Nov 20 '18 at 14:31
Wiktor KrólWiktor Król
62
While adding the autoprfixing task from the gulp-autoprefixer plugin I noticed the
autoprefixer({ cascade: false })
option. And this option was not clear for me what it is doing.
In the documentation I read that:
cascade (boolean): should Autoprefixer use Visual Cascade, if CSS is uncompressed. Default: true
So I compiled my SASS to the CSS with the cascade: false and with cascade true and I got the same result in both cases:
My SASS:
body
display: flex
p
display: flex
Compiled to the CSS with the autoprefixer({ cascade: false }):
body {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
body p {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
Compiled to the CSS with the autoprefixer({ cascade: true }):
body {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
body p {
display: -webkit-box;
display: -ms-flexbox;
display: flex; }
So my final question is - What the autoprefixer's cascade: false/true option is responsible for?
Thank you very much for the answer.
css gulp gulp-sass gulp-autoprefixer
css gulp gulp-sass gulp-autoprefixer
asked Nov 20 '18 at 14:31
Wiktor KrólWiktor Król
62
asked Nov 20 '18 at 14:31
Wiktor KrólWiktor Król
62
asked Nov 20 '18 at 14:31
Wiktor KrólWiktor Król
62
asked Nov 20 '18 at 14:31
Wiktor KrólWiktor Król
62
asked Nov 20 '18 at 14:31
Wiktor KrólWiktor Król
62
62
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I was actually also curious about this and noticed the following when cascade: true (which is the default):
given this:
body {
background: black;
display: flex;
flex-direction: row-reverse; }
autoprefixer outputs:
body {
background: black;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-orient: horizontal;
-webkit-box-direction: reverse;
-ms-flex-direction: row-reverse;
flex-direction: row-reverse; }
notice the indentations in the lines following -webkit-box-orient: horizontal;
however, if cascade: false:
body {
background: black;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-orient: horizontal;
-webkit-box-direction: reverse;
-ms-flex-direction: row-reverse;
flex-direction: row-reverse; }
answered Feb 6 at 2:31
rebelcl0udrebelcl0ud
111
add a comment |
I had the same question and this is what I found:
'To make your CSS look pretty, autoprefixer can cascade the prefixes—adding whitespace to make the prefixes line up (although, if you’re using the minification gulp plugin, it won’t make any difference in the end)'
-> https://www.futurehosting.com/blog/use-autoprefixer-to-speed-up-site-development/
answered yesterday
pollxpollx
518
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53395252%2fcascade-option-in-gulp-autoprefixer%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I was actually also curious about this and noticed the following when cascade: true (which is the default):
given this:
body {
background: black;
display: flex;
flex-direction: row-reverse; }
autoprefixer outputs:
body {
background: black;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-orient: horizontal;
-webkit-box-direction: reverse;
-ms-flex-direction: row-reverse;
flex-direction: row-reverse; }
notice the indentations in the lines following -webkit-box-orient: horizontal;
however, if cascade: false:
body {
background: black;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-orient: horizontal;
-webkit-box-direction: reverse;
-ms-flex-direction: row-reverse;
flex-direction: row-reverse; }
answered Feb 6 at 2:31
rebelcl0udrebelcl0ud
111
add a comment |
I was actually also curious about this and noticed the following when cascade: true (which is the default):
given this:
body {
background: black;
display: flex;
flex-direction: row-reverse; }
autoprefixer outputs:
body {
background: black;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-orient: horizontal;
-webkit-box-direction: reverse;
-ms-flex-direction: row-reverse;
flex-direction: row-reverse; }
notice the indentations in the lines following -webkit-box-orient: horizontal;
however, if cascade: false:
body {
background: black;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-orient: horizontal;
-webkit-box-direction: reverse;
-ms-flex-direction: row-reverse;
flex-direction: row-reverse; }
answered Feb 6 at 2:31
rebelcl0udrebelcl0ud
111
add a comment |
I was actually also curious about this and noticed the following when cascade: true (which is the default):
given this:
body {
background: black;
display: flex;
flex-direction: row-reverse; }
autoprefixer outputs:
body {
background: black;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-orient: horizontal;
-webkit-box-direction: reverse;
-ms-flex-direction: row-reverse;
flex-direction: row-reverse; }
notice the indentations in the lines following -webkit-box-orient: horizontal;
however, if cascade: false:
body {
background: black;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-orient: horizontal;
-webkit-box-direction: reverse;
-ms-flex-direction: row-reverse;
flex-direction: row-reverse; }
answered Feb 6 at 2:31
rebelcl0udrebelcl0ud
111
I was actually also curious about this and noticed the following when cascade: true (which is the default):
given this:
body {
background: black;
display: flex;
flex-direction: row-reverse; }
autoprefixer outputs:
body {
background: black;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-orient: horizontal;
-webkit-box-direction: reverse;
-ms-flex-direction: row-reverse;
flex-direction: row-reverse; }
notice the indentations in the lines following -webkit-box-orient: horizontal;
however, if cascade: false:
body {
background: black;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-orient: horizontal;
-webkit-box-direction: reverse;
-ms-flex-direction: row-reverse;
flex-direction: row-reverse; }
answered Feb 6 at 2:31
rebelcl0udrebelcl0ud
111
answered Feb 6 at 2:31
rebelcl0udrebelcl0ud
111
answered Feb 6 at 2:31
rebelcl0udrebelcl0ud
111
answered Feb 6 at 2:31
rebelcl0udrebelcl0ud
111
111
add a comment |
add a comment |
I had the same question and this is what I found:
'To make your CSS look pretty, autoprefixer can cascade the prefixes—adding whitespace to make the prefixes line up (although, if you’re using the minification gulp plugin, it won’t make any difference in the end)'
-> https://www.futurehosting.com/blog/use-autoprefixer-to-speed-up-site-development/
answered yesterday
pollxpollx
518
add a comment |
I had the same question and this is what I found:
'To make your CSS look pretty, autoprefixer can cascade the prefixes—adding whitespace to make the prefixes line up (although, if you’re using the minification gulp plugin, it won’t make any difference in the end)'
-> https://www.futurehosting.com/blog/use-autoprefixer-to-speed-up-site-development/
answered yesterday
pollxpollx
518
add a comment |
I had the same question and this is what I found:
'To make your CSS look pretty, autoprefixer can cascade the prefixes—adding whitespace to make the prefixes line up (although, if you’re using the minification gulp plugin, it won’t make any difference in the end)'
-> https://www.futurehosting.com/blog/use-autoprefixer-to-speed-up-site-development/
answered yesterday
pollxpollx
518
I had the same question and this is what I found:
'To make your CSS look pretty, autoprefixer can cascade the prefixes—adding whitespace to make the prefixes line up (although, if you’re using the minification gulp plugin, it won’t make any difference in the end)'
-> https://www.futurehosting.com/blog/use-autoprefixer-to-speed-up-site-development/
answered yesterday
pollxpollx
518
answered yesterday
pollxpollx
518
answered yesterday
pollxpollx
518
answered yesterday
pollxpollx
518
518
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53395252%2fcascade-option-in-gulp-autoprefixer%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
