- From: Boris Zbarsky <bzbarsky@mit.edu>
- Date: Wed, 07 Jan 2015 16:35:08 -0500
- To: whatwg@lists.whatwg.org
On 1/7/15 3:55 PM, Nicholas C. Zakas wrote: > Yeah, that works well if you're dealing with bleeding-edge browsers > only. Not so much elsewhere. Non-bleeding-edge browsers would also have the existing window.opener.location.href behavior, right? As in, asking for a spec change to the way the href setter works to work around lack of support for another part of the spec (rel=noreferrer) is only useful if you assume browsers would implement the change to the setter faster than they'll implement support for rel=noreferrer. I personally don' find that very likely, since rel=noreferrer is already shipping in at least Chrome and Firefox and doesn't require nearly the amount of web compat testing that the other change would. Or is the above just a general complaint, as opposed to a reason to change the behavior of the href setter? -Boris
Received on Wednesday, 7 January 2015 21:35:47 UTC