The default bug view has changed. See this FAQ.

e10s: propagate appId and isInBrowserElement from child to parent process

RESOLVED FIXED in mozilla17

Status

()

Core
Networking
RESOLVED FIXED
5 years ago
2 years ago

People

(Reporter: jduell, Unassigned)

Tracking

unspecified
mozilla17
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(blocking-basecamp:+)

Details

Attachments

(1 attachment)

Created attachment 644207 [details] [diff] [review]
v1

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

5 years ago
to our fake nsILoadContext on the *parent* :)

Comment 2

5 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

5 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/c6a54c7607ca
https://hg.mozilla.org/mozilla-central/rev/c6a54c7607ca
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
(Reporter)

Updated

5 years ago
Blocks: 777620
Blocks: 1188777
You need to log in before you can comment on or make changes to this bug.