- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Tue, 21 Aug 2012 14:30:06 -0400
- To: www-style@w3.org
On 8/21/12 2:21 PM, Tab Atkins Jr. wrote: > Actually, that seems about right. Having a common Declaration > interface for the things that use that seems useful, and then > subclassing the interface for each individual use lets you specialize > the list of exposed properties. If we want a common Declaration interface, should it have getPropertyPriority on it? Should it have a "cssText"? Should it even talk about "property"? Should it have a setProperty that takes a priority argument? I'm OK with the answer being "yes" to all of those, for backwards compat reasons, but it seems like having to define the property priority stuff behavior for various consumers like font-face is a bit annoying. -Boris
Received on Tuesday, 21 August 2012 18:31:46 UTC