From 41280031bf4f7c7c9b567c920cdd9fae83a825c7 Mon Sep 17 00:00:00 2001 From: Matt Hensman Date: Sat, 23 Feb 2019 22:15:38 +0000 Subject: [PATCH] Fix redundancy Fix redundancy --- IMPLEMENTATION.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/IMPLEMENTATION.md b/IMPLEMENTATION.md index 9e16bc9..4b44af6 100644 --- a/IMPLEMENTATION.md +++ b/IMPLEMENTATION.md @@ -8,7 +8,7 @@ When a request is intercepted, the `shim/content.js` script is executed in the c Messages passed to the shim are custom events of type `__castMessage`. Messages passed back from the shim are custom events of type `__castMessageResponse`. Event listening and creation is handled by the `shim/messageBridge.js` script. -The request is then redirected to the shim bundle (`shim/index.js`) which creates the `window.chrome.cast` API interface. +The request is then redirected to the shim bundle (`shim/index.js`) which creates the `window.chrome.cast` API object. The `shim/content.js` script creates a message port connection (named `shim`) to the background script through which messages from the shim (except `popup:/` messages) are forwarded to the background script. The connection triggers the background script to spawn a bridge application instance. The tab/frame ID is stored and used to associate shim instances with popup windows.