Iframe is a security trainwreck. You could clickjack Google's login widget iframe to steal account details as late as 2018, maybe even later.[1]
Whatever legitimate gripes you may have with AMP, it's not the same as iframes at all.
Iframe is a security trainwreck. You could clickjack Google's login widget iframe to steal account details as late as 2018, maybe even later.[1]
Whatever legitimate gripes you may have with AMP, it's not the same as iframes at all.
That seems like it should be relatively fixable. For example, iframes could be visible, clearly marked (including the URL), and sandboxed like any separate page. One could go further by insisting that they are display-only and can only be displayed rather than interacted with. Then an iframe would basically be a glorified jpg with a URL.
But if you just want to embed completely static article, I suppose it could work, but then there’s no incentive for anyone to allow them.
[1] Yes, I pulled that number out of my ____.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-...
Edit: looks like Safari, IE, and Edge don't check all ancestors which is a potential flaw. Chrome and Firefox do though.