Contacts API -- attribute order

Is there a particular reason for the diverging attribute order in some classes? Example:

[NoInterfaceObject]
interface  ContactField
 {
    attribute DOMString  type;
    attribute DOMString? value;
    attribute boolean    pref;
};

[NoInterfaceObject]
interface ContactAddress
 {
    attribute boolean    pref;
    attribute DOMString? type;
    attribute DOMString? formatted;
    attribute DOMString? streetAddress;
    attribute DOMString? locality;
    attribute DOMString? region;
    attribute DOMString? postalCode;
    attribute DOMString? country;
};

pref is last and then first.

Since this can be observed from JS, can we pick one meaningful order and stick to that for all classes?

Andreas

Received on Thursday, 25 August 2011 06:46:52 UTC