Enable the port message queue in /workers/opaque-origin.html - #11189

Ah yes, good catch. Seems 39051c9 changed the RemoteContext code from assigning the event handler to onmessage to instead just calling addEventListener. I do wonder if it might not make more sense to add the start call to that code in RemoteContext though, rather than having to update all tests using fetch_tests_from_worker? At least it seems like SharedWorker would have the same problem, unless that is handled somewhere generically already?

create_remote_worker calls start() for service workers and shared workers, and otherwise assumes a dedicated worker. This test falls into the dedicated worker code path but needs start(). Do you think this is OK as-is or should we change create_remote_worker to call start() if it exists?

Ah, good point. So then it's only the fairly esoteric case of passing a raw MessagePort. We could add a separate if (is_message_port(worker)) case just for that, but given how uncommon this likely is I suppose we might as well do changes like this.

We can implement that if it becomes more common ☺