Windtalk diagram

Windtalk provides A seamless way for two WINDows to TALK to each other.

Windtalk exports a function or an object from within an iFrame or Window. This can now be invoked from any other window.


How does code in one window communicate with an iFrame or another window?

The traditional way to do this is by passing messages (See postMessage). The host window will send a message to iFrame. iFrame will receive a message, parse the message and then call some code. The iFrame will then take the result of the code and then send a message to the host window with the result. The host window will now receive the message, parse it, and then call its own code.

In theory, this is fine. One can wrap this boilerplate message parsing to make the life easier. But when you have new code to add, you have to add another if clause in message parsing and then call the new code.

Wouldn't it be nice if we could just call the code in the other window like any other code! = 'Bilbo Baggins';
await objectInIframe.updateProfile();

This is possible if all the message boilerplate code is tethered behind a proxy.

This is where WindTalk comes in and provides you with that capability.

Let's consider a case where a parent window wants to interact with an object in an iframe.

In the iframe:

const color = {
red: 0,
green: 0,
blue: 0,
update: function () {
// update the ui

In parent window:

const color =; = 200; = 150; = 10;


View on Github for more details.