- From: Thomas Jensen <notifications@github.com>
- Date: Thu, 03 Dec 2015 04:25:07 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Thursday, 3 December 2015 12:25:57 UTC
@dylanb I have a bunch of use cases for which iframes are terribly cumbersome due to lack of a formal API and styling issues: ads, single authentication, embedded content (youtube, twitter-streams, Discourse) and payment windows. Have a look at the trouble this guy went through to support something that should be first-citizen on the web: http://benvinegar.github.io/seamless-talk/#/ I don't now the implementation details of this, but what makes you think you won't be able to detect a shadow DOM? I can imagine a simple test would do. Again, I don't know the details, but I don't see a conflict. As I understand it, this simply opens up more browser internals to web developers. I would guess that the underlying sandboxing is the same as used by iframes. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/100#issuecomment-161619636
Received on Thursday, 3 December 2015 12:25:57 UTC