`iframe` is one of the features that has required a lot of work to get right (it is a bit alien on the platform and has resulted in a lot of corner-cases) and which is referred to in multiple places and different specs. How are you going to handle all of these, like feature-policy, as pointed out by @dbaron above. We are a bit afraid that this feature will land and it will be a multi-year effort to make it integrate properly in the web platform, similarly to `iframe`s. I think that you can calm our nerves by going through specs mentioning `iframe` like HTML and look at all the cases and see if things would work as they are for `portal`s or need monkey patching. Like you need to define how this works for browsing contexts: https://html.spec.whatwg.org/multipage/browsers.html#windows Also check all cases involving `iframe`s like fully active etc. https://html.spec.whatwg.org/multipage/browsers.html#fully-active -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/331#issuecomment-479349814
Received on Wednesday, 3 April 2019 05:52:35 UTC