postMessage queues a runnable task, see https://html.spec.whatwg.org/multipage/webappapis.html#concept-task-runnable but the implied document is no longer fully active when we actually dequeue the runnable to run, but for PostMessageEvent we don't check if our implied document (or in this case targetWindow) is fully active. This part of the spec is unclear and under-specified (see https://github.com/whatwg/html/issues/4980) so it's not easy to say exactly what should happen here. This closes the gap in behavior between chromium/safari and firefox. Differential Revision: https://phabricator.services.mozilla.com/D310341
These are the cross-document messaging (postMessage()) tests for the
cross-document messaging chapter of the HTML Standard.