RE: no-cascade proposition

> Well yeah, but I don't think it's appropriate to fix stuff at html
> level just because it gives you problems on css level?
You essentially would like to select your markup independently of the container's and vice-versa, for the container to select its own markup and not yours. This is effectively namespacing and it will require markup-level declarations in order for the namespace qualifiers in your selectors to resolve to the right elements. I do not think you can avoid that; and the fact that you cannot is no proof there is a problem with CSS imo.

Received on Wednesday, 10 December 2008 17:13:38 UTC