Why JSON specification still isn't fixed to force key-value pairs in objects to be considered ordered?

Question

Reasons to do so seem to be very strong:

1. The requirement to keep JSON object fields order in many cases is very common. Just search the internet.
2. Even current JS engines now guarantee the order, probably after realization it is useful enough.
3. Such change in the specification will be at least forward compatible.
4. Transferred key-value pairs are ordered anyway in the serialized format so why not use it? While the order could be represented for free we are forced to ignore it and apply ugly workarounds with the current JSON spec.

Do you know any viable alternatives of JSON without such issues or any ways how to make this JSON quirk fixed?