nasko@ - can you please help with triage?  I am not sure 1) if this is important and 2) what we can do here (changing externally-facing API is more difficult than just changing //contents public API).

FWIW, the processes API is listed as experimental and restricted, so we can make breaking changes (though it'd be nice to somewhat limit them).

Assigning to nasko for triage.

More generally, there are several aspects of the old chrome.processes API that pre-date out-of-process iframes (OOPIFs) and need to be updated before the API is launched.  Nasko and I would be happy to consult but don't have time to spend on it in the short term.

I'm removing myself as the owner, since I don't plan on working on this anytime soon. Anyone is welcome to take this over so changing to "Available".

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

If we want to ship chrome.processes to stable, this needs to be fixed first.