I have referred a less file in the web page which has an imported file and I can change the variables using less.modifyVars method. Now I want to download the modified import less file, not parsing the CSS output. Is there any way to get the modified less file after using modifyVars?
For Example
Web.html:
<link rel="stylesheet/less" type="text/css" href="theme.less" />
base.less:
#header: #ffffff;
theme.less:
#import base.less;
.header{
color: #header;
}
common.js:
less.modifyVars({"header", "#000000"});
I want to get the modified base.less file with changes #header: #000000; Can I get the file?
This is my stylesheet declaration code:
<link rel="stylesheet" href="username-theme.css">
<link rel="stylesheet" href="layout.css">
"username-theme.css" filename vary, ie john123-theme.css or jenifer-theme.css
I'm trying to solve the following problem:
in my layout.scss I want to use following code:
body{color:$theme-color}
where $theme-color comes from john123-theme.scss
Have a look at the documentation.
so you can have a file smth like _variables.scss with your variables defined and then in your layout.scss you will include it like
#import 'variables';
so all the variables will be available there.
You could try importing the other way, and at the end of your user stylesheet, import layout.scss. as long as the variable is defined before the import, it's value will be used in the layout.scss contents. Then you'll just have to link the user css file into the page, because it now includes everything you had in layout.scss. ex:
_layout.scss
body{color:$theme-color}
username-theme.scss
//define variable
$theme-color: #fff;
//import
#import "layout";
I have coded a Landing page just to try Twitter Bootstrap with Less files.
I am not sure if I have organized my less files as it should be.
In the head section of my index.html:
<link rel="stylesheet/less" type="text/css" href="bootstrap.less" />
Here the content of my bootstrap.less
// Core variables and mixins
#import "less/variables.less"; // Modify this for custom colors, font-sizes, etc
#import "less/mixins.less";
// CSS Reset
#import "less/reset.less";
// Grid system and page structure
#import "less/scaffolding.less";
#import "less/grid.less";
#import "less/layouts.less";
// Base CSS
#import "less/type.less";
// Utility classes
#import "less/utilities.less"; // Has to be last to override when necessary
In my folder "less" i have the following files
utilities.less
utilities.css
variables.less
variables.css
grid.less
grid.css
type.less
layouts.less
mixins.less
scaffolding.less
reset.less
They are all actually necessary to make my landing page work but I am not sure if this file organization is the best solution.
I am bit confused about that, could you help me out and tell me if I am doing well? Is there a better way to organize the files?
Here you see the landing page
How you organize your files is entirely up to you, but here's how I normally do it during development:
public/
css/
layout.css (compiled from main.less)
less/
main.less (imports bootstrap/bootstrap.less)
bootstrap/
bootstrap.less
...etc...
Usually main.less also imports files like blog.less, forum.less, etc (depending on the site content). This schema lets me include layout.css in the HTML, and either compile the lesscss through a watcher, or on demand.
I have an html web design made by someone else; they have used #import inside the css files. I will for several reasons (primarily: http://www.stevesouders.com/blog/2009/04/09/dont-use-import/) to remove the #import inside the css files and instead include directly it in the html page with: <link rel="stylesheet"… >
My question is now: what will be the correct way to include the files via link to maintain the current rule validation sequence
Current #import sequence, eg.:
a.css
#import b.css
b.css
#import c.css
#import d.css
Will the correct link order be:
a.css
b.css
c.css
d.css
or is it something like:
c.css
d.css
b.css
a.css
or???
Each file contains, besides one or more import tags also own css rules.
For the record: it is not an option for me to gather all the files in one file – the different css files are used I different context alone and/or together
An #import rule includes all stylerules as if they were on that position. Example (default.css):
#import "first.css";
#import "second.css";
#import "third.css";
body {
color: #333333;
}
In this order, all css rules of first.css will be applied first, then the second.css, then the third.css. So if you want to remove the inclusion, just follow the import links and add them in this order in your html head section:
<head>
<title>Whatever</title>
<link href="first.css" rel="stylesheet" type="text/css">
<link href="second.css" rel="stylesheet" type="text/css">
<link href="third.css" rel="stylesheet" type="text/css">
<link href="default.css" rel="stylesheet" type="text/css">
</head>
So, in your case it will be:
c.css
d.css
b.css
a.css
I believe they will be parsed in the order they are presented to the browser, in linked style sheets the import rules must be before any other rules in the file or errors will occur so again I am assuming that they are parsed in order.
a.css
b.css
c.css
d.css
Post back if you find this not to be true.
Is it possible to include one CSS file in another?
Yes:
#import url("base.css");
Note:
The #import rule must precede all other rules (except #charset).
Additional #import statements require additional server requests. As an alternative, concatenate all CSS into one file to avoid multiple HTTP requests. For example, copy the contents of base.css and special.css into base-special.css and reference only base-special.css.
Yes. Importing CSS file into another CSS file is possible.
It must be the first rule in the style sheet using the #import rule.
#import "mystyle.css";
#import url("mystyle.css");
The only caveat is that older web browsers will not support it. In fact, this is one of the CSS 'hack' to hide CSS styles from older browsers.
Refer to this list for browser support.
The #import url("base.css"); works fine but bear in mind that every #import statement is a new request to the server. This might not be a problem for you, but when optimal performance is required you should avoid the #import.
The CSS #import rule does just that. E.g.,
#import url('/css/common.css');
#import url('/css/colors.css');
Yes.
#import "your.css";
The rule is documented here.
In some cases it is possible using #import "file.css", and most modern browsers should support this, older browsers such as NN4, will go slightly nuts.
Note: the import statement must precede all other declarations in the file, and test it on all your target browsers before using it in production.
Yes, use #import
detailed info easily googled for, a good one at http://webdesign.about.com/od/beginningcss/f/css_import_link.htm
yes it is possible using #import and providing the path of css file
e.g.
#import url("mycssfile.css");
or
#import "mycssfile.css";
#import("/path-to-your-styles.css");
That is the best way to include a css stylesheet within a css stylesheet using css.
The "#import" rule could calls in multiple styles files. These files are called by the browser or User Agent when needed e.g. HTML tags call the CSS.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="EN" dir="ltr">
<head>
<title>Using #import</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<style type="text/css">
#import url("main.css");
</style>
</head>
<body>
</body>
</html>
CSS File "main.css" Contains The Following Syntax:
#import url("fineprint.css") print;
#import url("bluish.css") projection, tv;
#import 'custom.css';
#import url("chrome://communicator/skin/");
#import "common.css" screen, projection;
#import url('landscape.css') screen and (orientation:landscape);
To insert in style element use createTexNode don't use innerHTML but:
<script>
var style = document.createElement('style');
style.setAttribute("type", "text/css");
var textNode = document.createTextNode("
#import 'fineprint.css' print;
#import 'bluish.css' projection, tv;
#import 'custom.css';
#import 'chrome://communicator/skin/';
#import 'common.css' screen, projection;
#import 'landscape.css' screen and (orientation:landscape);
");
style.appendChild(textNode);
</script>
Import bootstrap with altervista and wordpress
I use this to import bootstrap.css in altervista with wordpress
#import url("https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css");
and it works fine, as it would delete the html link rel code if I put it into a page
#import url('style.css');
As opposed to the best answer, it is not recommended to aggregate all CSS files into one chunk when using HTTP/2.0
I have created main.css file and included all css files in it.
We can include only one main.css file
#import url('style.css');
#import url('platforms.css');
Yes You can import easily one css to another (any where in website)
You have to use like:
#import url("url_path");
sing the CSS #import Rule
here
#import url('/css/header.css') screen;
#import url('/css/content.css') screen;
#import url('/css/sidebar.css') screen;
#import url('/css/print.css') print;
For whatever reason, #import didn't work for me, but it's not really necessary is it?
Here's what I did instead, within the html:
<link rel="stylesheet" media="print" href="myap-print.css">
<link rel="stylesheet" media="print" href="myap-screen.css">
<link rel="stylesheet" media="screen" href="myap-screen.css">
Notice that media="print" has 2 stylesheets: myap-print.css and myap-screen.css. It's the same effect as including myap-screen.css within myap-print.css.
I stumbled upon this and I just wanted to say PLEASE DON'T USE #IMPORT IN CSS!!!! The import statement is sent to the client and the client does another request. If you want to divide your CSS between various files use Less. In Less the import statement happens on the server and the output is cached and does not create a performance penalty by forcing the client to make another connection. Sass is also an option another not one I have explored. Frankly, if you are not using Less or Sass then you should start. http://willseitz-code.blogspot.com/2013/01/using-less-to-manage-css-files.html