I've gotten sign-off to do this from rockot@. The other step necessary to run these tests outside of a Chromium build is to export the generated Mojo JS bindings into a Chromium-specific directory within the Web Platform Tests repository as these are not normally shipped with Chrome.

Oops, I forgot this bug existed. Please don't do this.

We're transitioning to the new native Blink Mojo bindings very soon, and
you can already turn those on with --enable-blink-features=MojoJS

In fact you can already generate bindings which use the new JS API by
setting use_new_js_bindings to true in your mojom GN rule.

From there you can simply script src
${out}/gen/mojo/public/js/mojo_bindings.js and whatever generated mojom js
you need.

Thanks! I'll give it a try.

Note, we'll still need to land an alternative for getting at a connector,
but I have a CL in progress for that which will also be available behind a
simple blink RuntimeEnabled flag.

Do you have an issue number for that or can you link to the CL here?

I guess we've been lumping things into 699569 and 723923 as precursors for
this use case. No bug exists specifically for the new connector API. I can
file one.

I came here from https://lists.w3.org/Archives/Public/public-test-infra/2017AprJun/0057.html

Was this not fixed with --enable-blink-features=MojoJS,MojoJSTest, or is that something else?

This is obsolete. We don't use gin bindings anymore, and yes the MojoJs feature flag addresses the spirit of the bug anyway.