http://bit.ly/dhg6xI
For some reason that I cannot understand when I move my css from the html
to the css file (even when I leave the conditional code in the html) the
css messes up. Why on earth is this happening? Very strange. Maybe the
onpage css takes precendce over the external css?
Ed wrote:
http://bit.ly/dhg6xI
For some reason that I cannot understand when I move my css from the html
to the css file (even when I leave the conditional code in the html) the
css messes up. Why on earth is this happening? Very strange. Maybe the
onpage css takes precendce over the external
css messes up. Why on earth is this happening? Very strange. Maybe the
onpage css takes precendce over the external css?
I haven't looked at your URL, but the order of precedence is inline,
embedded, and then external. You may be changing the cascade order by
moving some of the styles from
On 19 February 2010 17:03, l...@ljonn.com wrote:
I haven't looked at your URL, but the order of precedence is inline,
embedded, and then external. You may be changing the cascade order by
moving some of the styles from embedded to external.
No. There is no difference in cascade order
ed asked:
http://bit.ly/dhg6xI
For some reason that I cannot understand when I move my css from the
html
to the css file (even when I leave the conditional code in the html) the
css messes up. Why on earth is this happening? Very strange. Maybe the
onpage css takes precendce over the
David Dorward said:
There is no difference in cascade order between embedded and external.
Not so fast. If the link to the external stylesheet preceeds the style
element - which is common - styles declared in the style element come
before in the cascade because of source order, ie being
