[codecook]

I have already read in multiple areas that the proper way to link a external stylesheet is placing something like "<link rel="stylesheet" type="text/css" href="http://www.mycss.css" />" in the head of the document. However, I currently can only place that line in the body and it works fine.

My question is, is it only a matter of time before browsers may stop supporting linking items in the body and I should really try to figure out a way to put link the CSS in the head?

Second question is, if I define the same exact selector in two different linking stylesheets with 2 different paramaters, will the one further down always overwrite the top stylesheet?

e.g.

<link rel="stylesheet" type="text/css" href="http://www.mycss.css" /> ---- p {color:green;}
<link rel="stylesheet" type="text/css" href="http://www.mycss2.css" /> ---- p {color:red;}

Will <p> now always(unless otherwisedefined by html in document) be red?


Thanks!!

This post has been edited by codecook: 14 June 2012 - 07:20 AM

[Dormilich]

codecook, on 14 June 2012 - 04:19 PM, said:

Second question is, if I define the same exact selector in two different linking stylesheets with 2 different paramaters, will the one further down always overwrite the top stylesheet?

AFAIK, that is a set rule in CSS.

[codecook]

Dormilich, on 14 June 2012 - 07:22 AM, said:

codecook, on 14 June 2012 - 04:19 PM, said:

Second question is, if I define the same exact selector in two different linking stylesheets with 2 different paramaters, will the one further down always overwrite the top stylesheet?

AFAIK, that is a set rule in CSS.

Thanks for confirming my second question.

Do you know what the issue with the 1st question? Is it still supposed to work fine in the body of the document and is only recomended to use in the Head because of some caching issue so it does not have refetch the css ?

[Dormilich]

as far as my experience goes, browsers will try their best to render any served HTML code, no matter how invalid it is. I don’t think they will ignore <link>s in the wrong place anytime soon.