Open
Bug 1023701
Opened 11 years ago
Updated 3 months ago
Stop using ContentParent static methods in child process
Categories
(Core :: DOM: Content Processes, task, P5)
Core
DOM: Content Processes
Tracking
()
NEW
People
(Reporter: kanru, Unassigned)
Details
It is confusing when we call ContentParent static method in the child process. We should factor out these method into a common class or namespace.
For example ContentParent::StartUp and ContentParent::CreateBrowserOrApp
|
||
Updated•7 years ago
|
Priority: -- → P5
|
|
||
Updated•7 years ago
|
|
Assignee | |
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
|
||
Updated•3 years ago
|
Severity: normal → S3
|
||
Updated•7 months ago
|
Type: defect → task
Component: DOM: Core & HTML → DOM: Content Processes
|
||
Comment 1•3 months ago
|
||
CreateBrowserOrApp doesn't seem to exist, but ContentParent::StartUp does. It immediately checks if we're in the parent process and bails if we're not. I don't think it is super confusing but seems fine if somebody wants to think of a better way to do this.
You need to log in
before you can comment on or make changes to this bug.
Description
•