Open Bug 1559973 Opened 6 years ago Updated 3 years ago

Unify process types by extending GeckoProcessTypes enum with Content Types

Categories

(Core :: IPC, enhancement, P3)

57 Branch
enhancement

Tracking

()

People

(Reporter: tarek, Unassigned)

Details

Should we unify process types for clarity ?

Right now we have :
https://searchfox.org/mozilla-central/source/dom/ipc/ContentParent.h#52-59

And content subtypes:
https://searchfox.org/mozilla-central/source/xpcom/build/GeckoProcessTypes.h#26

My use case is to simplify ChromeUtils::RequestProcInfo() code

Flags: needinfo?(nfroyd)

I think it is desirable to merge them. Content process checks would presumably need to use some function, then, to check for content process subtypes?

Flags: needinfo?(nfroyd)

FYI Whatever solution is done for this will also have to handle the webIsolated=... process types used by fission-enabled browsers.

We currently put a dynamic string after the = with the site-origin of the website we're loading to ensure a separate process is used for each site-origin.

The priority flag is not set for this bug.
:jld, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jld)
Type: defect → enhancement
Flags: needinfo?(jld)
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.