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

> The <iframe> is already in the closed shadow tree and window.frameElement returns it, as they are in the same node tree.

Right, I get that.

> Then it's wrong. What breaks the encapsulation is that you pull the src parameter from shadow host and put it in the closed shadow tree in the first place.

I get that too.  The problem is there's no specified way of transparently providing a custom iframe that is encapsulated from both sides.  In my situation the `contentWindow.frameElement` is useless to the content and is, essentially, a stumbling block to both our library and the content author.  For all intents and purposes of the content author, the custom element _is_ the frame element.

It's possible that in the frame setup, we could override the property (it's non-configurable in some browsers, though, so that's not feasible right now), but I feel that this would be better as the default.

---
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-221853328