News for hackers. Stuff that matters.
Re:About rel=noopener (2016) by stephenr on Thursday January 25, 2018 @07:50AM (#16230451)
HTML 2.0 was published in 1995.

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

Re:About rel=noopener (2016) by beaconstudios on Thursday January 25, 2018 @08:10AM (#16230539)
I'm aware of that - the existing HTML versions have been pretty much incremental though. XHTML was a breaking change but more for syntactical reasons. By a "2.x" version I mean a fresh rewrite with no requirements for parity with previous versions, so the lessons of the current engine can be applied in a clean-slate environment.
Re:About rel=noopener (2016) by stephenr on Thursday January 25, 2018 @08:58AM (#16230765)
i feel like there must be an xkcd that sums up your suggestion...
Re:About rel=noopener (2016) by illustrioussuit on Thursday January 25, 2018 @09:15AM (#16230852)
Re:About rel=noopener (2016) by beaconstudios on Thursday January 25, 2018 @10:19AM (#16231325)
I'm not sure that applies here but it could definitely suffer from the Second System Effect - https://en.wikipedia.org/wiki/Second-system_effect