Ted Drake wrote:
IE6 will get buggy if you only use imports.
Are you referring to FOUC - or other bugginess or both? If there are
other bugs can you enlighten me?
kind regards
Terrence Wood.
***
List Guidelines:
Tim wrote:
I reckon you are being cynical Barney :-)
Consider colour blindness, 8% of adult males, you can allow a user to
select a colour scheme.
Consider screen size, alternative stylesheets can improve presentation
of different devices.
I use seven different linked stylesheets on
Check this out Barney.
A use of the before property to add the characters name before their
dialogue, for comprehension as well as accessibility. Select stylesheet
two.
http://www.hereticpress.com/Dogstar/Novels/NUNC.html
on-page devices to switch this
The Onpage device is Javascript or
What is the current best practice for style sheets - imported or
linked - and why?
Bob
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help:
Using the @import stylesheet rule is great if you only want your stylesheet
rules to be picked up by most modern browsers. Netscape 4 and below and IE 4
and below do not support the @import rule. This allows you to target
stylesheets to specific browser versions.
Does that make sense?
On
Makes sense and I already knew that.
The reason behind my post has to do with me noticing a trend towards
importing style sheets and I was curious if this was the current
best practice and if so, why.
Bob
Using the @import stylesheet rule is great if you only want your
stylesheet rules
Grant Novey wrote:
Using the @import stylesheet rule is great if you only want your
stylesheet rules to be picked up by most modern browsers. Netscape 4 and
below and IE 4 and below do not support the @import rule. This allows
you to target stylesheets to specific browser versions.
Does that
Bob
I believe what you may have seen is the practice of
having link type=text/css rel=stylesheet href= media=screen in the
page body for xhtml validation purposes
having a raft of @import statements in the linked CSS file
The principle being to modularise your CSS, having multiple separate CSS
Rob,
I've been modularizing like this for years:
link href=../../as/cs/com.css rel=stylesheet type=text/css
media=screen
link href=../../as/cs/p7pmv0.css rel=stylesheet type=text/css
media=screen
link href=../../as/cs/thickbox.css rel=stylesheet type=text/
css media=screen
Am I doing
There's a good explaination here:
http://www.unix.org.ua/orelly/web/html/ch09_01.html
(Scroll down to 'Linked Versus Imported Style Sheets')
Dave.
From: Bob Schwartz [EMAIL PROTECTED]
Reply-To: wsg@webstandardsgroup.org
To: wsg@webstandardsgroup.org
Subject: [WSG] style sheets - best
Linked css (and if @import is maintained, a css link after the embedded
style) resolves certain flash of unstyled content IE6 bugs.
Regards,
Barney
Bob Schwartz wrote:
Rob,
I've been modularizing like this for years:
link href=../../as/cs/com.css rel=stylesheet type=text/css
media=screen
explaination here:
http://www.unix.org.ua/orelly/web/html/ch09_01.html
(Scroll down to 'Linked Versus Imported Style Sheets')
Dave.
From: Bob Schwartz [EMAIL PROTECTED]
Reply-To: wsg@webstandardsgroup.org
To: wsg@webstandardsgroup.org
Subject: [WSG] style sheets - best practices
Date: Thu, 15
Schwartz [EMAIL PROTECTED]
Reply-To: wsg@webstandardsgroup.org
To: wsg@webstandardsgroup.org
Subject: [WSG] style sheets - best practices
Date: Thu, 15 Mar 2007 11:57:51 +0100
What is the current best practice for style sheets - imported
or linked - and why?
Bob
Hi all
I used to think that modularizing css was a grand idea. It certainly makes
it easier to maintain your code.
At Yahoo!, we have a huge responsibility to reduce our server demands and
make pages load as fast as possible. We have found that it is actually
better to have one enormous css file
Barney,
Do you have any idea where that article was or who wrote it? I'd like to
read this.
Thanks
Ted
A while back I read this article on the secret power of the rel property
in links... The author went about listing examples of different objects
you could link and different terms for what
Bob,
on Thursday, March 15, 2007 at 15:59 wsg@webstandardsgroup.org wrote:
I've been modularizing like this for years:
link href=../../as/cs/com.css rel=stylesheet type=text/css
media=screen
link href=../../as/cs/p7pmv0.css rel=stylesheet type=text/css
media=screen
link
Ted Drake wrote:
So, if you are building a site that gets moderate to low traffic, go
for the multiple css files and import or link. If you are building a
site that will get significant traffic and your server load is
important, you should consider consolidation.
Hi Ted,
I think this link was
On 15 Mar 2007, at 14:26:40, Barney Carroll wrote:
Grant Novey wrote:
Using the @import stylesheet rule is great if you only want your
stylesheet rules to be picked up by most modern browsers. Netscape
4 and below and IE 4 and below do not support the @import rule.
This allows you to
I reckon you are being cynical Barney :-)
Consider colour blindness, 8% of adult males, you can allow a user to
select a colour scheme.
Consider screen size, alternative stylesheets can improve presentation
of different devices.
I use seven different linked stylesheets on everypage, hardly
19 matches
Mail list logo
