Re: [w3c/webcomponents] shadow tree -> iframe <- contentWindow.frameElement encapsulation issue (#507)

what has this to do with shadow DOM? The document inside shadow iframe is loaded just like a normal document in iframe and has access to the containing iframe if that is accessible with non-shadow iframe.
So, this doesn't seem to have anything to do with shadow DOM encapsulation.

Perhaps iframe could have a property/attribute indicating that window.frameElement should be null in the contained window. Or hmm, still sounds more like a sandboxing thing. Should the iframe's document just be treated as a cross-domain document, so communication would need to happen via postMessage.


But it is a bit unclear to me what the goal here is.

---
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/webcomponents/issues/507#issuecomment-221909786

Received on Thursday, 26 May 2016 15:43:27 UTC