RE: Proposal of @ua

[Todd Russell wrote]
> When the browser detects an "open and", it will try to parse the
> following block and if it comes across something it cannot handle
> properly, if will just fail over to the @else.  This spares extra

Depending on the CSS implementation, you may not know at the time of parsing whether or not a block is completely valid or whether or not your browser supports the case. For instance, many unknown declarations are simply carried with the rule set as expando properties which can later be retrieved through script or by inspecting the textual output of the style sheet. This makes getting into the else block very difficult. This is also why the cascade option works, but doesn't work, since you can't guarantee that an entire rule set will be thrown out, only that the specific declaration will be thrown out or ignored which does generally work.


Received on Wednesday, 28 November 2007 11:17:19 UTC