This project is a proof-of-concept of an idea about how to isolate sourceless/same-domain iframes by using revocable proxies to build a membrane around the iframe realm.
Compared with isolated/cross-domain iframes, sourceless iframes offer the ability to synchronously communicate with the main page with objects and functions. This power comes at the cost of increased chances for memory leaks because it enables inside-of-iframe code to become entangled with code outside the iframe.
In this project, we are attempting to solve this problem by building a "membrane" that intercepts communication between iframe code and main window code with proxies. When objects from the iframe pass over the membrane, they are replaced with a revocable proxy. This enables us to cleanly break all retainers between the iframe and the main window when it is removed, which should (if implemented comprehensively) completely eliminate the chance of iframe realm memory leaks.
For more details see it running live.
- Clone this repo by running
git clone https://github.com/astegmaier/playground-iframe-membranes.git - Change into the directory by running
cd playground-iframe-membranes - Ensure nodejs and yarn classic is installed.
- Install dependencies by running
yarn. - Run
yarn start. - Open
http://localhost:8080/in your browser.
Project uses jest to run unit tests.
to execute, simply run yarn test
Test suites are run against membrane implementations specified in the .env file. To run tests against a particular membrane or set of membranes, look for that solution's "number" in the file name, and add it to the JEST_MEMBRANE variable in the .env file.
For example, to test 1-baseline and 3-harmony-reflect-example, modify the file to contain JEST_MEMBRANE=1 3
test run information is given in the console, or as HTML in the jest_html_reporters.html file.