Re:Google launches new “portal” HTML element
by mshockwave on Friday May 10, 2019 @05:22PM
(#19882372)
that's also my first impression of this article. but i (hope) believe google is aware of this security concern, otherwise they'll probably be the next Microsoft
Google search is Windows?
Re:Google launches new “portal” HTML element
by dillondoyle on Friday May 10, 2019 @07:07PM
(#19883118)
It says that it only allows postMessage for cross domain communication.
BUT I'm concerned it doesn't mention similar sandbox and feature policies as iFrame. It also mentions that it will allow the 'child' to know if it's inside a portal with window.portalHost but at least this github mentions you can minimally declare no-referrer https://github.com/web-platform-tests/wpt/blob/master/portal...
Wouldn't the concern be ads ( I assume this is what this feature is intended for especially on mobile )? If there are no similar restrictions as a iframe safeFrame I can see a ton of ad scams that take advantage...
Luckily, uBlock Origin can block all portal tags entirely.
Re:Google launches new “portal” HTML element
by burtonator2011 on Friday May 10, 2019 @05:51PM
(#19882577)
My expectation is that you could only do this for the same domain.
If that is true, how would that interact with signed exchanges[0]?
[0] https://developers.google.com/web/updates/2018/11/signed-exc...
Re:Google launches new “portal” HTML element
by stevens32 on Friday May 10, 2019 @06:35PM
(#19882905)
Looks like that's not the case based on the blog post linked in the article https://web.dev/hands-on-portals/
I love how they gloss over the security issue here. This is the equivalent of “we made a new Ajax that can call from different domains.”
Reading through the article, I don’t see the security restriction addressed at all. I expect that this gets worked on when google submits this to the w3c to be made part of html.