Customize: Failed to execute 'postMessage' on 'DOMWindow'

[feedmymedia]

Guys, I'm receiving this message in my console when I try to use Customizer:

customize-base.js?ver=4.7-alpha-38178-src:753

Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('http://tests.mamp') does not match the recipient window's origin ('http://tests.mamp:8888').

As you can see, I'm running a localhost with a specific port. I can change the port for this test if this issue happens only for me.

I downloaded from the master branch few minutes ago: ​git://develop.git.wordpress.org/

Thank you! And sorry if this issue is not appropriated here.

Screenshot:

[westonruter]

Originally reported at ​https://github.com/xwp/wordpress-develop/issues/178

[westonruter]

@feedmymedia @mh-themes would you please give 38409.1.diff​ a try?

[westonruter]

​https://github.com/xwp/wordpress-develop/commit/13e4b19ae58074b9bca4959a7892d0ec5c13a9ad

[feedmymedia]

@westonruter it's working perfect now: postMessage and XWP new feature (Additional CSS). Thank you!

Replying to westonruter:

@feedmymedia @mh-themes would you please give 38409.1.diff​ a try?

[MH Themes]

@westonruter Has this been committed to trunk yet? We've tested the changes but for us the issue still remains, but maybe it's a mistake on our end. We'll test again as soon as it's committed to trunk and report back.

[westonruter]

In 38890:

Customize: Harden url matching to account for varying ports and ensuring matching base pathname for allowed urls

Fixes #38409.

[westonruter]

@MH-Themes No, it wasn't committed yet. I was providing a patch to test with. But it is now committed in r38890.

[MH Themes]

@westonruter Thanks a lot, just tested the latest version in trunk and the issue is fixed.

[westonruter]

In 38926:

Customize: Fix logic inversion in determining whether a URL is previewable which prevented previewing anything but homepage.

Fixes regression introduced in [38890].

See #38409.
Fixes #38492.

[westonruter]

In 40318:

Customize: Fix navigation of site in preview on IE11.

Addresses issue in IE11 where the default port number of :80 is unexpectedly included on link.host for links dynamically created by scripts.

Props westonruter, afercia for testing.
See #38409.
Fixes #40198.

[swissspidy]

In 40335:

Customize: Fix navigation of site in preview on IE11.

Addresses issue in IE11 where the default port number of :80 is unexpectedly included on link.host for links dynamically created by scripts.

Props westonruter, afercia for testing.
See #38409.
Fixes #40198.

Merges [40318] to the 4.7 branch.

[mattwiebe]

Found another "fun" bug related to this in IE11 for https sites: the :443 port also gets spuriously added, causing the postMessage bridge to fail.

Patch incoming, can move this to a new issue if needed, but this is where the work for port 80 was already done.

[westonruter]

In 40381:

Customize: Fix HTTPS navigation of site in preview on IE11.

Accounts for HTTPS links (port 443) where [40318] only accounted for HTTP links (port 80). Addresses issue in IE11 where the default port number is unexpectedly included on link.host for links dynamically created by scripts.

Props mattwiebe.
Amends [40318], [38890].
See #38409.
Fixes #40198.

[swissspidy]

In 40386:

Customize: Fix HTTPS navigation of site in preview on IE11.

Accounts for HTTPS links (port 443) where [40318] only accounted for HTTP links (port 80). Addresses issue in IE11 where the default port number is unexpectedly included on link.host for links dynamically created by scripts.

Props mattwiebe.
Amends [40318], [38890].
See #38409.
Fixes #40198.

Merges [40381] to the 4.7 branch.