Disowning openers in targeted navigations

[lucasgadani]

I'm looking at fixing chromium bug https://bugs.chromium.org/p/chromium/issues/detail?id=651661 , but looking at the spec it's not entirely clear to me what should be done per spec, as well as different browser have different behaviors.

In particular, the spec says that (https://html.spec.whatwg.org/#the-rules-for-choosing-a-browsing-context-given-a-browsing-context-name):

If name is not an ASCII case-insensitive match for "_blank" and there exists a browsing context whose name is the same as name, and current is familiar with that browsing context, and the user agent determines that the two browsing contexts are related enough that it is ok if they reach each other, then set chosen to that browsing context. If there are multiple matching browsing contexts, the user agent should set chosen to one in some arbitrary consistent manner, such as the most recently opened, most recently focused, or more closely related.

In this case, 'new' is still false when choosing a browsing context, so it looks to me that Chrome is following the spec (https://html.spec.whatwg.org/#following-hyperlinks):

Let target and replace be the result of applying the rules for choosing a browsing context given targetAttributeValue, source, and noopener.
If target is null, then return.
If noopener and replace are true, then disown target's opener.

In this case, that target's opener is not disowned.

A few points that should be clarified:

• What to do for targeted subframe navigations vs top-level navigations? Firefox has different behavior between noopener and noreferrer for targeted subframe navigations (https://html.spec.whatwg.org/#link-type-noreferrer).

• When disowning an opener, should the opener still be reachable by name? Edge always allows windows to be reached by name, Chrome and Firefox don't.

[lucasgadani]

Duplicate of #1826.