Switch to multipage ECMAScript spec links

[domenic]

It'd make people happy to not have to load the singlepage, and it'd be consistent with how the Bikeshed ecosystem links to the HTML multipage spec.

We should not just prefix links with /multipage/ because then viewers incur a client-side redirect and the point is to make viewers happier.

[annevk]

@marcoscaceres @dontcallmedom is this something the new terminology database can help with? Having a proper index of ECMAScript would be great, it handling multipage similar to HTML multipage would be even better.

[dontcallmedom]

we have an open issue on extracting definitions from the ecmascript spec - having WebIDL as a consumer would certainly help put more efforts in it.

That being said, I don't think bikeshed is able to use the webref definitions database yet, although I know @tabatkins has been working on it.

I'll add a comment to the issue above to mention the preference to use the multipage version of the spec.

[tabatkins]

Oh that would be very nice, yes.

Bikeshed will be using webref Real Soon Now; I think I've only got two blockers left that I'm trying to fix upstream, and will just patch in Bikeshed otherwise.

[dontcallmedom]

https://github.com/w3c/webref/blob/master/ed/dfns/ecmascript.json now has hopefully most of the needed ecmascript definitions linked to the multipage version of the spec; once bikeshed lands support for webref, they should be usable from the WebIDL spec.