Intent to implement and ship: disown opener in a targeted navigation when noopener is used

[Lucas Gadani]

Contact emails l...@chromium.org Spec https://github.com/whatwg/html/issues/1826 Summary When targeting links with rel=noopener the opener should always be disowned. That means this: <a href='' target='foo'>Click me first</a> <a href='' target='foo' rel='noopener'>Click me second</a> will open two different windows. The same behavior is expected when using window.open('', 'foo', 'noopener'). Motivation Disowning the opener allows the browser to make better decisions about whether to launch a new renderer process for the new window.

We also want to achieve interoperability with other browsers when it comes to the 'noopener' behavior.

Interoperability risk Firefox: Shipped Edge: No public signals Safari: No public signals Web developers: No signals Compatibility risk

Firefox initially shipped an implementation that disowned both 'noopener' and 'noreferrer' but they found that disowning 'noreferrer' was not web-compatible (https://bugzilla.mozilla.org/show_bug.cgi?id=1358469).

The intent here is to implement this only for 'noopener'. Firefox ships this since 52.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes or no. Yes.

OWP launch tracking bug https://crbug.com/651661 Link to entry on the Chrome Platform Status https://www.chromestatus.com/features/5641309343711232 Requesting approval to ship? Yes.

[Rick Byers]

Sounds reasonable to me, just a couple questions:

Do we have any stats on how often "noopener" is used, to form an upper bound on the potential for breakage?  Mike, what's your judgement on the compat risk?

What's the plan for getting the spec and web-platform-tests updated for this?

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALQVofrmUM3Nq8S2%2BjXdUn3_BoYR10D2HhTUKdxBeURToo0K3Q%40mail.gmail.com.

[Boris Zbarsky]

On 11/3/17 1:01 PM, Rick Byers wrote:
> What's the plan for getting the spec and web-platform-tests updated for
> this?

There are some tests for this already. See
http://w3c-test.org/html/browsers/the-window-object/window-open-noopener.html
and
http://w3c-test.org/html/semantics/links/links-created-by-a-and-area-elements/htmlanchorelement_noopener.html

As for the spec getting updated... it's somewhat waiting on you guys
saying whether you're actually on board with the specific proposals
involved and explaining what it is, exactly, you're planning to
implement. See https://github.com/whatwg/html/issues/1826 where I've
been waiting for a response for the last 6 months or so.

-Boris

[Philip Jägenstedt]

Lucas, can you work on getting https://github.com/whatwg/html/issues/1826 resolved, with tests, matching what it is you'd like to implement and ship here? If there's some part of it that is in doubt and needs to be proven web compatible before being changed in the spec, tentative tests may be of use.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68130a50-19cd-1772-5e44-591f376918e7%40mit.edu.