Skip to content

Use only the incumbent global in postMessage#1573

Merged
domenic merged 1 commit into
masterfrom
postmessage-globals
Jul 20, 2016
Merged

Use only the incumbent global in postMessage#1573
domenic merged 1 commit into
masterfrom
postmessage-globals

Conversation

@domenic

@domenic domenic commented Jul 19, 2016

Copy link
Copy Markdown
Member

Previously one of the origin checks was performed with the entry
settings object, while the origin and source attributes of the resulting
MessageEvent were derived from the incumbent settings object. At least
WebKit and Blink appear to use the same global for both, and it makes
sense to align the checks on the same global.

The difference is only observable in test cases that fiddle with
document.domain, as entry and incumbent are always same origin-domain
(but, in document.domain cases, not always same origin).

Fixes #1542. Helps #1431 but hurts #1430.


I don't think this needs needs review from Boris or Bobby since any editor should be able to verify this just implements what was discussed in #1542, so I'll avoid pinging them.

Previously one of the origin checks was performed with the entry
settings object, while the origin and source attributes of the resulting
MessageEvent were derived from the incumbent settings object. At least
WebKit and Blink appear to use the same global for both, and it makes
sense to align the checks on the same global.

The difference is only observable in test cases that fiddle with
document.domain, as entry and incumbent are always same origin-domain
(but, in document.domain cases, not always same origin).

Fixes #1542. Helps #1431 but hurts #1430.
@annevk

annevk commented Jul 20, 2016

Copy link
Copy Markdown
Member

This looks good. I filed #1579 for other problems I noticed while reviewing.

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

Development

Successfully merging this pull request may close these issues.

2 participants