- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Mon, 29 Nov 2004 18:15:37 -0600
- To: Kurt Cagle <kurt@kurtcagle.net>
- CC: www-svg@w3.org
Kurt Cagle wrote: > I would second Antoine's comment, and see it as a problem that's > coming up more and more often as the CSS vocabularies expand. These are > also likely to collide with areas such as XUL (consider that XUL has a > tooltip attribute, and an overlay element). The XUL tooltip attribute doesn't have anything to do with CSS, and only applies to elements in the XUL namespace (being an attribute that's only defined for those elements). The overlay element is just in the XUL namespace. The key issue raised here is that CSS is cascaded for all elements in a document, so you can't just say that some CSS properties don't have a defined value for some particular node. Then, if all nodes have values of all CSS properties, you have to specify what those properties do to those nodes.... > Please note that the CSS > property /float/ requires a number of workarounds in most languages How so, exactly? The DOM bindings use cssFloat, not float, and any other time "float" will be a string... Given that, perhaps the issues you see with "static" should be clarified a bit? Examples of it causing problems would help. -Boris
Received on Tuesday, 30 November 2004 00:15:49 UTC