Re: [heycam/webidl] Enumeration order of interface members (#432)

Here's what I think Web developers might reasonably expect order to be:

1. members are ordered alphabetically (case insensitive), just like in dev tools,
1. members are ordered lexicographically, and
1. members are ordered as listed in the spec (without really thinking that some APIs are split-up through partials, mixins, and different documents).

I have no idea what the perf cost of (1) and (2) would be. I find them sort of attractive if they're not too expensive.

The problem with (3) is that we're unclear what it means precisely. Could we settle on something were we say:

- order within a single definition is respected,
- order in between definition is vendor-specific,
- overloads across multiple definitions might show up with any of those in a vendor specific way.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/432#issuecomment-334584519