Closed
Bug 793909
Opened 12 years ago
Closed 12 years ago
on B2G, replace include file with a B2G specific hosted one
Categories
(Core Graveyard :: Identity, enhancement)
Core Graveyard
Identity
Tracking
(blocking-basecamp:+)
RESOLVED
INVALID
blocking-basecamp | + |
People
(Reporter: benadida, Unassigned)
References
Details
Reporter | ||
Updated•12 years ago
|
blocking-basecamp: --- → +
Comment 1•12 years ago
|
||
Anant has pointed me to http observers, which look like just the ticket:
https://developer.mozilla.org/en-US/docs/XUL_School/Intercepting_Page_Loads#HTTP_Observers
Updated•12 years ago
|
Blocks: basecamp-id
Comment 2•12 years ago
|
||
On b2g, each app has its own cookie jars. Given this design, login state cannot be shared across apps, so the shim is not going to work as intended on the device.
:benadida, should we close this as a wontfix or invalid?
Comment 3•12 years ago
|
||
nav.mozPay uses the system app's cookie store so it shouldn't matter which app calls it. We should have the same behavior for nav.id?
Reporter | ||
Comment 4•12 years ago
|
||
Lucas: we were looking to first implement with the shim to get work done while parallelizing the system cookie store work. We just realized that won't work, so I am indeed marking this bug invalid.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Updated•12 years ago
|
No longer blocks: basecamp-id
Updated•6 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•