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

@annevk That plan sounds good to me. I like how it's insensitive to implementation-specific extended attributes, whitespace differences, etc., and how it's easy to run in your head. I don't think people will run into the theoretical ambiguity (when static members may share names with non-static members).

To spell it out a bit further, the order could be:
1. The main interface (or namespace or module)
1. Partial interfaces (sorted by the concatenation of names)
1. Included interface mixins (sorted by the name of the interface mixin), closing #473

Seems like we have room to change things here, as browsers disagree with each other in enumeration order already. For example, in `Document`, Chromium and Webkit put `implementation` first, whereas Gecko puts `getElementsByTagName` first--and this is just in the "easy case" of things declared in the interface itself. 

-- 
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-469268345