Gunlaug Sørtun wrote:
Tony Crockford wrote:
and having caught up with my reading, the use of CC's seems to be
frowned upon.
I can't see why - as long as CC's are used to serve a minimal number
of fixes to _old_ IE/win versions. Old browsers are "fixed in time".
It is when one starts a design-process by preparing CC's for "fixing"
IE7 (and maybe even later versions) that I feel it is time to stop and
think. It is bad enough that we get new buggers to deal with, but we
should not promote and preserve such a buggy trend, IMO.
'bugs' is the word you want. Your sentiment in using the other word is
acknowledged.
But 'bugs' could do?
_
_j[_
Larry
since I mostly use the CC's for max width and max height, what's the
simplest alternative, that would:
a) put "hacks" in separate stylesheets for IE6, IE5 and IE5 on Mac.
/*\*//*/
@import url("macie.css");
/**/
...works for IE5 on Mac, and...
b) the best _valid_ hack to solve max-width and max-height issues.
...the @import hack...
<http://www.gunlaug.no/contents/wd_additions_12.html>
...works for IE/win, and is perfectly valid. It is IE/win that is
broken.
Whether it is the "best", or even a "good" hack, or not, is something
I can't answer. I dislike hacks, but I'll continue to use them as
long as I find them necessary for "fixing" old and weak browsers.
The fact that IE7 also "get" the @import hack is an added bonus. Looks
like IE7 needs a bit of help anyway.
and why?
Basically, I want to keep my source-code as free from browser-specific
solutions as I possibly can. That means I also like to avoid having
CC's in there - whenever I can. If I can solve a problem on
stylesheet level, then I'll go for that - even if it's ugly.
could I have an import rule within the CSS that would be conditional
for the different IE's - do I need to be that specific?
Once you have an IE/win specific stylesheet that the validator can't
see, you can use as many valid or non-valid @imports and/or other
hacks as you need to separate versions.
Some variants here...
<http://imfo.ru/csstest/css_hacks/import.php>
...and you don't have to bother about which other browsers a hack may
target, since they are prevented from seeing the first IE/win specific
stylesheet and subsequently can't see any hacks within it.
regards
Georg
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
