Kay Smoljak wrote:
At least you will know where to look, instead of trying to work out
which combination of backslashes and asterisks fixed the particular
issue for which version.
One would hope that this information would already be somewhere in your
head when you implemented the hack.
If the real issue is that hackers are fundamentally stupid, that's a
problem separate from the inherent pitfalls of different techniques.
Conditional comments do have that feature of giving you a template of
sorts, a structure to your additional rules. And without that guidance
(plus general criticism), hackers are more likely to end up on their
own, working without the benefit of convention, and quite possibly
writing a big confusing jumble.
One method is to write all your IE hacks at the bottom of the relevant
stylesheet. You can have
/* The civilised world */
...
...
/* IE 7 compensations */
...
/* IE 6 compensations */
...
...which would make things easier to allocate in a similar way to
arranging things in separate css files. However this
compartmentalisation is one of the reasons I dislike conditional
comments - with pages that rely on heavily different techniques you end
up having to sift through so much css, computing it or looking at it
through different windows, that it's just not worth it. I recommend
grouping them together, so that you can look up your selector and see
*everything* that can possibly be computed for objects answering those
description. So if my object requires different rules for different
browsers, I will put them there and then, one after the other:
object{}
object,{}
* html object{}
Of course, when I put it this way, I realise that Rafael's hack has the
problem of being limited to objects which already have a class -
selectors such as the following can't be converted:
*,{} div,{} #id,{}
Clever but inflexible.
Regards,
Barney
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
