On Mon, Sep 19, 2011 at 1:33 PM, Nick Morgan <[email protected]> wrote: > On 19 September 2011 11:56, Samuel Richardson <[email protected]> wrote: >> From memory, most browsers will keep the order intact with the exception of, >> weirdly enough, Chrome. > > I don't think it's *that* weird actually. If Chrome was doing > something off-spec then it would be weird, but the fact that the spec > says there is no order means it's actually *useful* for Chrome to do > it differently, as it stops developers from relying on a coincidence.
>From what I have read, Chrome developers decided to have properties ordered in a different way and that was actually considered "useful" to speed up properties access time in Chrome. Best of all, they also realized that specifications was giving them the right to do so. -- Diego > -- > Nick Morgan > http://skilldrick.co.uk > @skilldrick > > Save our in-boxes! http://emailcharter.org > > -- > To view archived discussions from the original JSMentors Mailman list: > http://www.mail-archive.com/[email protected]/ > > To search via a non-Google archive, visit here: > http://www.mail-archive.com/[email protected]/ > > To unsubscribe from this group, send email to > [email protected] > -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
