Skip to content

Conversation

@zcorpan
Copy link
Member

@zcorpan zcorpan commented Nov 5, 2025

This effectively removes a cross-origin communication channel. Fixes #2486.

(This is on top of #11881.)

  • At least two implementers are interested (and none opposed):
  • Tests are written and can be reviewed and commented upon at:
  • 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.)


/document-lifecycle.html ( diff )
/document-sequences.html ( diff )
/dom.html ( diff )
/rendering.html ( diff )


<p>Each <code>Document</code> has a boolean <dfn
data-x="document-embedder-has-margin-attributes">embedder has margin attributes</dfn>, initially
false.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does caching it here mean we want it to be able to be different across navigations? Including possibly being different between a bfcache back and an ordinary back?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Sort out cross-browser incompatibilities in handling of iframe marginwidth/marginheight if only one is set

3 participants