Closed Bug 807894 Opened 7 years ago Closed 4 years ago

When you add a web page as a home-screen app, the app doesn't get your login cookie

Categories

(Firefox OS Graveyard :: Gaia::Homescreen, defect)

x86_64
Linux
defect
Not set

Tracking

(blocking-basecamp:-)

RESOLVED WONTFIX
blocking-basecamp -

People

(Reporter: dholbert, Unassigned)

References

Details

(Keywords: b2g-testdriver, unagi)

I just logged in to http://getpocket.com/ and then starred it & added it to my home-screen.

When I launched the app from my home-screen, it made me log in again.

This makes me think we're not copying the site's cookie over to the generated web-app's profile. Seems like that would be a good idea, so users don't have to log in again.
(To be clear: I know webapps have their own isolated cookie-jars, distinct from the browser. But it'd be nice if, when you create a webapp from a site that you're logged into, we initialize its cookie jar with your login cookie for that site, so you don't have to login again.)
This is likely a side effect of our "data jars" work.  CC'ing Fabrice and Jonas to clarify.
Would be pretty cool to have this, but it's not a blocker at this point.
blocking-basecamp: ? → -
Component: Gaia → Gaia::Homescreen
Mass update: Resolve wontfix all issues with legacy homescreens.

As of 2.6 we have a new homescreen and having these issues open is confusing. All issues will block bug 1231115 so we can use that to re-visit any of these if needed.
Blocks: 1231115
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.