News for hackers. Stuff that matters.
Re:About rel=noopener (2016) by Forge36 on Thursday January 25, 2018 @07:45AM (#16230431)
Internet Explorer tried to maintain multiple rendering engines. Every version from IE5 to IE11 (if you open the debug console you can switch rendering modes) And now they have Edge. It never took off.

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.

Re:About rel=noopener (2016) by beaconstudios on Thursday January 25, 2018 @08:11AM (#16230545)
this is why I say it would have to be opt-in through something like a header or tag on the page in question (although I don't think doctype would work well for this). Existing sites would use the current engine and sites that explicitly stated they were for the new engine would be handled differently.
Re:About rel=noopener (2016) by manigandham on Thursday January 25, 2018 @01:45PM (#16233347)
That's exactly what IE did with the `X-UA-Compatible` meta tag. It's just more work for both browsers and websites to manage, which is why it's not used anymore.

https://msdn.microsoft.com/en-us/library/jj676915(v=vs.85).a...

Re:About rel=noopener (2016) by kijin on Thursday January 25, 2018 @11:47AM (#16232220)
Content-Security-Policy might be a good way to opt in to this kind of behavior.