>> Yes, but I was actually trying to point out the opposite problem. CSS may be
>> a "standard", but a Pivot skin's style properties (by design) are not. So
>> you would have to stay on top of any changes that the skin developers decide
>> to make. In fairness, a style such as "font" isn't likely to change all that
>> often - I'm just pointing out a potential weakness in the design.
>
> I don't think this limitation of coupling to skins is specific to CSS. The
> CSS parser I've written assumes that when you specify some font-related
> properties, you're changing the "font" style of a component. Isn't that what
> "{ font: {bold: true} }" does? It assumes you're changing the "font" style?
No, it assumes that you are calling setFont() on the skin. It doesn't know
anything about "font" or "{bold:true}". The definition of the supported styles
is entirely up to the skin implementation.
