At 12/18/2006 01:58 AM, Barney Carroll wrote:
Geoff Pack wrote:
Gunlaug Sørtun wrote:
So, old hacks like the 'star html' hack for
IE6 (and older versions) is now "perfectly
valid" IMO, while hacks relying on bugs that
have survived into IE7, are extremely unsafe.
'extremely unsafe'? I'd say they are safe until
Microsoft releases another IE version. With
their track record, that could be *years*.
Given the choice between littering my html
(thousands of pages) with conditional comments,
or adding couple of hacks to a single CSS file,
I'll take the hacks, thank you very much.
Despite all the doomsayers, I had zero problems
with pages breaking when IE7 came out.
cheers
Geoff.
I agree with this. If we're going for zen
purity, I agree that theoretically hacks could be a liability.
But seriously, how many years have you been
telling yourself the star hack is unsafe? What
did that lack of safety ever mean?
Same as it means now -- the likelihood that
someday your code will fail because it depends on
the coincidence of two unrelated bugs in an evolving software product.
Lack of support for multiple classes can hardly
be called a 'bug' at this point. It's more like a 'feature'.
Only if you accept Microsoft's bugs as standards in preference to the W3C spec.
It's slightly arrogant to believe that you can
exploit a program's invisible weaknesses to
cover its visible others; but it's more naive to
believe that Microsoft would tackle hacks like
this. Seriously - if you're going to ascribe
IE's dev team the virtue of wanting to tackle
IE's problems, you'd think their priority list
would start with rendering flaws and end with
"let's see how css coders are fixing our browser and screw it up for them".
Given their recent work on IE7, I don't think
it's too naive to ascribe to them a desire to fix
their software to match the spec:
______________________
To match a subset of "class" values, each value must be preceded by a ".".
Example(s):
For example, the following rule matches any P
element whose "class" attribute has been assigned
a list of space-separated values that includes "pastoral" and "marine":
p.marine.pastoral { color: green }
This rule matches when class="pastoral blue aqua
marine" but does not match for class="pastoral blue".
http://www.w3.org/TR/CSS21/selector.html#class-html
______________________
Lack of support for multiple classes can hardly
be called a 'feature' at this point. It's more like a 'bug'.
Regards,
Paul
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
