On Fri, Aug 24, 2012 at 3:13 PM, Glenn Adams <glenn@skynav.com> wrote: > On Sat, Aug 25, 2012 at 1:12 AM, Tab Atkins Jr. <jackalmage@gmail.com> > wrote: >> An alternative is just to hack around WebIDL here, and simply state >> that the interface has a number of additional attributes of this form, >> which map (as specified) to the CSS property obtained by transforming >> the name by <specify camelCase to dash-separated>. > > Which would need to be qualified with "If and only if a UA semantically > supports property x, then it shall implement "partial interface > CSSStyleDeclaration { DOMString x; }" etc, since as we have seen above, UAs > are presently not implementing attributes for unsupported properties. Or > would you mandate they support the attribute in any case, returning null if > not semantically supported? In the last paragraph, I meant "a number of additional attributes" to refer to the set of properties that you support. Sorry, I wasn't quite writing spec text there. ^_^ ~TJReceived on Friday, 24 August 2012 22:31:28 UTC
This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:20 UTC