BroadcastChannel allows scripts from the same origin but other browsing contexts to send each other messages. Channels are scoped to an origin and have a name, messages posted to a channel will be delivered to all listeners of that channel in all documents. There’s already a Chromium bug for this: http://crbug.com/161070
SharedWorker allows same-origin messaging but with extra process/thread overhead and script plumbing.
Existing cross-document messaging relies documents having references to each other. Communication between two pages on the same origin is possible through less efficient and less expressive means such as cookies, local databases, server round-trips, SharedWorker or Flash’s LocalConnection. MessageChannel can be used, but only if the documents can bootstrap the channel somehow. Use cases include simply notifying other tabs when a user logs in or out so that they can refresh, coordinating multimedia playback so that background tabs can pause when a user requests playback in a foreground tab, and coordinating the use of storage resources.
The compatibility risk is low. This exposes a new, extremely simple interface rather than modifying an existing one. Mozilla is currently implementing this (https://bugzilla.mozilla.org/show_bug.cgi?id=966439) and there are some spec clarifications (http://bit.ly/1vTCQLE) coming out of that process.
Internet Explorer: No signals
Safari: No signals
Ongoing technical constraints
Will this feature be supported on all five Blink platforms (Windows, Mac, Linux, Chrome OS and Android)?
OWP launch tracking bug?
Link to entry on the feature dashboard
Requesting approval to ship?
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.