Rob Crowther wrote:
Gunlaug Sørtun wrote:
The "hiding" effect gained by 'CC' is used by many to justify hacking and to declare their solutions valid - because the validator doesn't complain.

It is ultimately laziness, but I don't want to have to expend the mental effort to distinguish between invalid CSS that is the result of a mistake and invalid CSS that is the result of hacking around IE.
 Or put another way, I don't want to get into the habit of being used
 to seeing my CSS not validate with the automatic test.

Well, since "valid" doesn't mean "applied according to standard", I have
to proofread my CSS anyway. I can't rely on the validator more than on
the spell-checker in the email client I use, so I do indeed distinguish
between "mistakes" and "intentional hacking" - regardless of whether the
latter are valid or not.

It would be nice if the validator would flag "nonsensical" combinations
of properties/values, so I could see at a glance where combinations like...
Element {
float: left;
margin: 6px;
display: inline;
}
...have been used, since "valid" combinations like that only serve the
purpose of killing an old browser bug. The usefulness of the validator
reports would be so much greater then.

This works for all browsers - with a bit of care.

I assume here you mean 'all current major desktop browsers'?

One has to draw the line somewhere, but I often check beyond the "major
desktop browsers" if I apply one of the potentially more disturbing
workarounds. How far I go depends on the case, the major user-group and
the client.
Whether or not a "disturbance" is acceptable, also depends on how
"standard compliant", implicit also how "current", the "disturbed"
browser is. That outweighs how "major" a browser in need of a workaround
is - in most cases.

regards
        Georg
--
http://www.gunlaug.no


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to