Re: [css-background] Order of properties in background shorthand

On 6/1/12 7:26 AM, Sebastian Zartner wrote:
> 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

No idea.

> and UAs like Firefox make the efforts to change the order when it's not necessary

You're confusing "make efforts to change the order" and "don't make 
efforts to preserve the order".

Let's take a simple example: background.  Internally this is stored as 
values for background-position, background-image, etc, with no 
particular ordering imposed on them (they're just members of a struct). 
  The original string is not stored anywhere, since it's not needed for 
normal operation and would take up extra memory.  When asked for 
.background, Gecko just serializes this unordered representation, which 
implies picking an arbitrary order at that point.

-Boris

Received on Friday, 1 June 2012 15:06:56 UTC