- From: Sylvain Galineau <sylvaing@microsoft.com>
- Date: Tue, 9 Dec 2008 15:05:03 -0800
- To: Niels Matthijs <niels.matthijs@internetarchitects.be>, "www-style@w3.org" <www-style@w3.org>
> Shifting the problem to html is an option, though it's really a styling > issue related to the workings of css and html-wise there should be > little interest in determining whether a piece of code is internal or > external. If the rules for your stand-alone component are being overridden by the document's cascade, you would not be able to override their cascade:enabled declaration so I assume this property would have to have only one negative state ? As Jens points out, it's also not clear which part of the cascade you are proposing to disable. If I understand it right, your markup is integrated into a larger document, the CSS rules of which you do not want to apply to your code. But then you surely expect cascade and inheritance to apply within your own code. It is as if you really wanted the equivalent of an iframe (as pointed out by Boris) so an HTML/markup level solution to delimit the boundary does seem appropriate.
Received on Tuesday, 9 December 2008 23:05:45 UTC