Closed
Bug 1188777
Opened 9 years ago
Closed 9 years ago
e10: use originAttributes from child to parent process.
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
firefox42 | --- | affected |
People
(Reporter: allstars.chh, Assigned: allstars.chh)
References
Details
In Bug 775861 we added appId/isInBrowserElement in Necko, now we should convert them to use originAttributes.
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → allstars.chh
Assignee | ||
Comment 1•9 years ago
|
||
Found out Bug 776174 already converted appId/IsInBrowserElement to SerializedLoadContext.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Comment 2•9 years ago
|
||
Do we need to do something special for userContext? Will it also need to converted to SerailizedLoadContext in order to work in e10s?
Assignee | ||
Comment 3•9 years ago
|
||
I am not a Necko expert, but I have already added originAttributes into SerializedLoadContext in Bug 1165466, I think it should work for userContext, as long as userContext is set correctly like bug 1195881. But perhaps check bug 1125916, it looks they want to replace it to LoadInfo.
Comment 4•9 years ago
|
||
userContext is part of OriginAttributes and they are serialized so userContext does not need special treatment.
You need to log in
before you can comment on or make changes to this bug.
Description
•