Dictionary members should be ordered lexicographically per Web IDL Standard about webauthn

[emlun]

I'll keep #2082 open because layout consistency is good for readability even when not formally required.

Is there any recommendation at all on the order of fields?

For how RPs should order fields in JavaScript representations of the options objects: no, order should not matter at all.

The low-level CTAP protocol does care about serialization order, but that's a different protocol which is not exposed to web applications and is not defined in WebIDL.

[emlun]

I think this order only applies to the internal dictionary representation that determines things like iteration order. I don't think it's meant to be enforced for parsing values in language bindings. I'll have to review the WebIDL spec some more before I'm sure, but I don't think there's any issue with the spec examples.

[zacknewman]

Honestly I know next to nothing about Web IDL. I only started looking at it since you mentioned it in #2082. If the order does not matter, then presumably #2082 should be closed? Is there any recommendation at all on the order of fields? Lexicographic order like Web IDL? Source definition order? In the RP library I am writing, I initially adhered to the source definition order when serializing data, but I then switched to the order mentioned in Web IDL. I realize it likely does not matter what order I use, but I'd rather use the "safest" order if there is one.