Closed
Bug 775861
Opened 12 years ago
Closed 12 years ago
e10s: propagate appId and isInBrowserElement from child to parent process
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
People
(Reporter: jduell.mcbugs, Unassigned)
References
Details
Attachments
(1 file)
|
(deleted),
patch
|
jdm
:
review+
|
Details | Diff | Splinter Review |
New fields in nsILoadContext (needed for data jars for cookies, appcache, localStorage, IndexedDB) must be propagated from child process to our fake nsILoadContext on the child. I have ideas about centralizing some of this code to avoid duplication. Not a priority now IMO.
Attachment #644207 -
Flags: review?(josh)
|
Reporter | |
Comment 1•12 years ago
|
||
to our fake nsILoadContext on the *parent* :)
|
||
Comment 2•12 years ago
|
||
Comment on attachment 644207 [details] [diff] [review] v1 Sigh, so much boilerplate.
Attachment #644207 -
Flags: review?(josh) → review+
blocking-basecamp: --- → +
|
|
Reporter | |
Comment 3•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/c6a54c7607ca
|
||
Comment 4•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/c6a54c7607ca
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
Blocks: 1188777
You need to log in
before you can comment on or make changes to this bug.
Description
•