28821 2015-06-16 18:25:45 +0000 add rel=newcontext 2016-03-08 09:33:36 +0000 1 1 1 Unclassified WHATWG HTML unspecified PC All RESOLVED FIXED P2 normal Unsorted 1 sbeards ian annevk mathias mike sworkman contributor oldest_to_newest 121117 0 sbeards 2015-06-16 18:25:45 +0000 This proposal is an attempt to resolve the window.opener.location.href issue with cross-origin (and same-origin UGC?) navigations when target="_blank". This issue has been discussed previously[1] and a bug[2] in chromium has existed since 2013. Besides using "rel=noreferrer" or setting window.opener=null via javascript there appears no clean solution to this problem. I propose that a new rel=newcontext attribute be added which can be used to inform user agents that the navigation should be done in a new browsing context and, as a result, window.opener should be set to null. Many publishers wish to allow a referrer to be sent and the Referrer Policy[3] is moving towards a spec where there is more granular control over the document-level and even the link-level value of Referer (sic). Many sites wish to send the origin, for instance, and in these cases they cannot use "rel=noreferrer". This leaves them only Javascript to deal with this issue. I think there should be a way to do this via HTML only. Here is a quick summary and demo of the issue[4]. I've prepared a PR to the spec here[5]. [1] https://lists.w3.org/Archives/Public/public-whatwg-archive/2015Jan/0002.html [2] https://code.google.com/p/chromium/issues/detail?id=168988 [3] http://w3c.github.io/webappsec/specs/referrer-policy/ [4] http://hardstatics.com/thrower.html [5] https://github.com/w3c/html/pull/22 123007 1 annevk 2015-09-02 05:38:06 +0000 Sorry for getting back to you so late. Our GitHub repository is actually here: https://github.com/whatwg/html. Are there any browsers interested in implementing your proposal that you know? 125380 2 mathias 2016-03-08 09:33:36 +0000 https://github.com/whatwg/html/pull/290