- From: Ben Kelly <notifications@github.com>
- Date: Mon, 19 Jun 2017 07:25:18 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 19 June 2017 14:26:02 UTC
> FYI. I tested the snippet in #1091 (comment) on Chrome. It doesn't seem to reuse the existing window of about:blank document. The state set to the global object is lost after the navigation.
Yes, I did some compat testing and @bzbarsky pointed out the only real use where browsers maintain compat is this:
```
<!doctype html>
<!-- top.html -->
<html>
<body>
<!-- declaratively defined iframe -->
<iframe src="nested.html" id="nested"></iframe>
<script>
// Modify the iframe's global synchronously before it loads. The resulting nested.html
// iframe will have its `window.foo` property set even though we are applying it to
// initial about:blank document here.
let frame = document.getElementById("nested");
frame.contentWindow.foo = "foo";
</script>
</body>
</html>
```
What do you think the various properties on FetchEvent should be for this situation?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1091#issuecomment-309455780
Received on Monday, 19 June 2017 14:26:02 UTC