Chrome Version: 61.0.3163.71, 62.0.3201.0
OS: Win10

What steps will reproduce the problem?
(1) Visit http://csreis.github.io/tests/window-open.html
(2) Click "Open simple window"
(3) In DevTools, see the value of window.opener in the second tab.
(4) Navigate the second tab to http://www.chromium.org via the omnibox (cross-process).
(5) Now check the value of window.opener.

What is the expected result?

In both cases, the opener should look like:
> Window {frames: Window, postMessage: ƒ, blur: ƒ, focus: ƒ, close: ƒ, …}

What happens instead?
After the process swap, the opener looks like:
> undefined {window: , self: , location: Location, closed: false, frames: , …}

This affects OOPIFs as well (e.g., window.parent, frames[0]).

Not sure if there's a functionality problem due to this, or if it's just cosmetic.