From: Adam Thompson <email@example.com> To: Kevin Carhart <firstname.lastname@example.org> Cc: email@example.com Subject: Re: proposed postMessage rev Date: Sun, 2 Jan 2022 18:28:39 +0000 [thread overview] Message-ID: <YdHu18cxBpeHzTNZ@pinebook-pro> (raw) In-Reply-To: <firstname.lastname@example.org> On Wed, Dec 22, 2021 at 07:37:53PM -0800, Kevin Carhart wrote: > I think we chewed on a couple of changes to postMessage but they aren't in yet. What do you think of the following? > > The differences are > (1) we are supposed to consider port (as in, networks, 80, 443, not talking about MessageChannel stuff here) when passing or failing the origin test > (2) setting me.origin = my$win().location; > (3) Adding an else case to the origin test so that if the postMessage can't run, we can be alerted that it didn't If it's not already added, it all looks sensible to me.
prev parent reply other threads:[~2022-01-02 18:27 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-23 3:37 Kevin Carhart 2022-01-02 18:28 ` Adam Thompson [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=YdHu18cxBpeHzTNZ@pinebook-pro \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: proposed postMessage rev' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).