Closed Bug 775861 Opened 7 years ago Closed 7 years ago

e10s: propagate appId and isInBrowserElement from child to parent process

Categories

(Core :: Networking, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
mozilla17
blocking-basecamp +

People

(Reporter: jduell.mcbugs, Unassigned)

References

Details

Attachments

(1 file)

Attached patch v1Splinter 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)
to our fake nsILoadContext on the *parent* :)
Comment on attachment 644207 [details] [diff] [review]
v1

Sigh, so much boilerplate.
Attachment #644207 - Flags: review?(josh) → review+
https://hg.mozilla.org/mozilla-central/rev/c6a54c7607ca
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
Blocks: 777620
You need to log in before you can comment on or make changes to this bug.