https://en.wikipedia.org/wiki/Framekiller
It's one of those situations where "This was mis-designed with insufficient eye towards how right bastards could use it, but the cat is out of the bag. We can't change the spec because it'll break legitimate uses of this technology, so this is the best option we have." Similar to how images were naively scoped to be embeddable from any web domain and then people invented pixel bugs, but you can't change the security model around image loading without breaking vast swathes of the existing web.
That's never been sufficient to keep bad actors out because end-users don't grok the URL bar.
This attack is superior to a mirroring attack because it uses the target site's own UI resources, so it looks very legit (no need to pay someone to monitor the UI of the target site for changes and rework your exploit to attack them).
On the other side chromium devs need to develop quirks/hacks for specific sites in order to support their bloated javascript hacks (:
I find it bizzare.