Tobie Langel

So are you suggesting we should just no spec this for now?

> Or we can just enforce the relative order of members declared in the definition of an interface in a single IDL fragment, though that does cause questions like this:...

> Well, can't we leave inter-IDL fragment order undefined/implementation-defined? I don't really have a strong opinion on this beyond wanting to resolve the current contradiction in the spec and needing...

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

Here's a manually filtered list I build for #363 based on [running awk on Gecko's src files](https://gist.github.com/tobie/bb83f160e93a084afdfb74ae29fddf2a#file-legacynio): * Geolocation * Coordinates * Position * PositionError * DeviceAcceleration * DeviceRotationRate *...

Well, we'd want to make sure suddenly exposing these interfaces to the Web doesn't break stuff, no?

Prefixing is an observable change. No idea if it would have real impact, though.

```js navigator.geolocation.getCurrentPosition(p => console.log(Object.prototype.toString.call(p))); // [object Position] ```

@annevk wrote: > I think what would help is not landing the IDL PR until the necessary downstream bugs are filed. Unless they're acted on immediately, this won't prevent either...

Translation tooling should be relatively easy to build on top of Bikeshed and ReSpec's parser, or as a standalone tool to use in post processing.