Defer updating the reused window's associated document until activation

[shannonbooth]

For discussion purposes, this is the fix for #12415 mentioned in that issue. It is as far as I can tell is correct by deferring setting the associated document until activation.

I'm not sure of what approach would have the best model here. Maybe instead there needs to be a more explicit distinction here between the Window's associated Document and the browsing context's currently active Document during this transient state (maybe window needs a "current" document?).

• At least two implementers are interested (and none opposed):
  • …
  • …
• Tests are written and can be reviewed and commented upon at:
  • https://github.com/web-platform-tests/wpt/blob/1cd72b546cd6b3b0a667b8af7c788aad29ed1869/html/webappapis/scripting/processing-model-2/integration-with-the-javascript-job-queue/promise-job-entry-different-function-realm.html
• Implementation bugs are filed:
  • Chromium: …
  • Gecko: …
  • WebKit: …
  • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): …
  • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): …
• Corresponding HTML AAM & ARIA in HTML issues & PRs:
• MDN issue is filed: …
• The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)

---

/browsing-the-web.html ( diff )
/document-lifecycle.html ( diff )