>> So what I get out of this discussion is that the order, in which a
>> browser returns the properties of a shorthand property via
>> getComputedStyle(), is not dictated. Is that correct?
> It really depends on the property.
> For example, these two declarations:
> font: 12px Times;
> font: Times 12px;
> are not equivalent. The former is valid, and the latter is not.
Right. Of course for other shorthand properties like "margin" there is also a specific order defined. So instead of "a shorthand property" I should have written "this shorthand property".
> As another example, these two declarations:
> font: 12px bold Times;
> font: bold 12px Times;
> are both valid, but don't mean the same thing. The former means a
> normal weight 12px font of the "bold Times" family, while the latter
> means a bold 12px font of the "Times" family.
Well, font was always a special candidate. I was following the discussion about keywords in unquoted font family names .
> What the spec does not dictate is the order in which things separated
> by "||" in the "Value" line are serialized.
Ok. So when there is no predefined order for the values the question is just why the order of the existing properties was changed in the current spec and UAs like Firefox make the efforts to change the order when it's not necessary (and obviously unwanted due to the response the Firebug team got from different sides).