That does nothing for deployed sites that aren't actively developed? Browser devs have decided those sites are worth not breaking.
If browsers enforce HTTPS in a similar way, I don't see why they shouldn't enforce better security elsewhere as well.
I suspect the cost of breaking web compatibility intentionally to accomplish this goal would kill a browser, as authentication, payment, and many other things would suddenly break.
https://msdn.microsoft.com/en-us/library/jj676915(v=vs.85).a...
Version # is not the phrase you want to overload. HTML5 is the latest version and was released 4 years ago.
I doubt this behaviour comes purely under html anyway as its only usable from the javascript environment.
More likely is a content security policy... oh looke there: https://w3c.github.io/webappsec-csp/#directive-disown-opener
Or mobile: https://m.xkcd.com/927/
Since this is still a problem, I'd say the web needs a way to gracefully migrate away from bad decisions like window.opener being available across origins.
Should we not decide that cross-origin window.opener is now deprecated, show big fat warnings on the developer console when it's used, and remove it in a year or two? I'd like an option to completely turn it off on my browser. Like third-party cookies, cross-origin access to just about anything is a bad idea.