3 ms·
If portals really were iframes, there would be no reason to create them. Google is completely open about their intentions. Citation from https://github.com/WIC
by altfredd 7y ago
If portals really were iframes, there would be no reason to create them.
Google is completely open about their intentions. Citation from https://github.com/WICG/portals/blob/master/key-scenarios.md https://github.com/WICG/portals/blob/master/key-scenarios.md:
> After being activated, a portal opened by the news aggregator will now receive the input events. This means that it will have to co-operate with the news aggregator in order to maintain the desired user experience.
Why exactly does it _have_ to cooperate? And _how_ can it cooperate? Will it be enough to include a script from parent domain? Will analytics be part of "desired user experience"? Will parent domain ban a site from it's index for trying to "break out"?
It is essentially impossible to build relationships of mutual trust to the point when one website can freely embed another... unless one party has overwhelming power advantage. Who is the target auditory of <portal>? What "news aggregator" has enough leverage to make pages switch back to it as told to? If such "aggregator" existed, I would not trust it to make web browsers or dictate, how they should work.
- tauwauwau 7y agoDoesn't it just mean that both sides have to maintain postMessage() handling? Just like host and iframe with different origins. Google will not be able to receive any events/messages unless they're sent by not-google.com. That's what I understand from it, please correct me if I'm wrong.
- altfredd 7y ago> Google will not be able to receive any events/messages unless they're sent by not-google.com Exactly: the integration requires cooperation from both websites, and there is zero reasons, why child website would want to cooperate. Unlike, say, using Google Analytics, letting user leave you via <portal> tag is against website's best interests.