[whatwg] DOMTokenList is unordered but yet requires sorting

> Ensuring consistency between browsers, to reduce the likelihood that any
> particular browser's ordering becomes important and then forcing that
> browser's ordering (which could be some arbitrary ordering dependent on
> some particular hash function, say) into the platform de facto.
> This is similar to what happened to ES property names -- they were
> supposedly unordered, UAs were allowed to sort them however they liked,
> and now we are locked in to a particular order.

I strongly think the order should not be sorted, but should reflect the order of the token in original string which was broken down into tokens.
It would also make implementations much simpler and sane, and would spare extra cpu cycles by avoiding the sort operations.

Received on Tuesday, 9 June 2009 16:00:21 UTC