- From: Garret Wilson <garret@globalmentor.com>
- Date: Mon, 21 Aug 2000 10:53:23 -0700
- To: <www-dom@w3.org>, "Blaine Brodie" <bbrodie@savagesoftware.com>
Blaine, Ah, there's the catch. Knowing which property a CSSValue is for will certainly help implementation, given that a CSSValue can be rendered in several ways depending on the property. Whether or not such a design is very elegant is a different matter, and I guess that, with CSS already having several ways to represent lists, there may not be much else that can be done. Thanks for pointing that out. Garret ----- Original Message ----- From: "Blaine Brodie" <bbrodie@savagesoftware.com> To: <www-dom@w3.org>; <garret@globalmentor.com> Sent: Monday, August 21, 2000 9:35 AM Subject: Re: CSSValueList and cssText > garret@globalmentor.com writes: > >1. A CSSValueList is a CSSValue. CSSValue must return a cssText value, > >which > >is how the value should be represented in the document. Therefore, > >CSSValueList should return a cssText value. > > > >2. A CSSValueList has no knowledge of which property name its values are > >for. > This is where you have been mislead. The specification states: > "The CSSValue interface represents a simple or a complex value. A > CSSValue object only occurs in a context of a CSS property." If the > CSSValue had no knowledge of its property then there would be a problem > with both the retreival of cssText and the parsing of the text during a > set. Hope this helps. > --- > Blaine >
Received on Monday, 21 August 2000 13:53:37 UTC