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

I didn't mention cross domain content.  Just third-party.  Damn, this is hard 😅.  Instead of using an iframe, a developer would use my component to load same origin content.

> Also, what kind of widget would need to pass pointer to itself to the iframe content.

The use case for that is the same as the reason an iframe content page might want to access `window.frameElement`.  In this case, it doesn't make any sense to expose the iframe element and the other implementation details of the shadow tree.

> This still feels like a sepatate feature from shadow dom, and something to opt-in.

Like I said, it only applies to iframes in a shadow tree, so I don't see how it could be separate.  Opt-in, maybe, but that's easy if WebKit fix their non-configurable `frameElement` binding.  I was merely pitching the idea as this seems to me like the option we'd want to use to keep implementation details hidden.

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