897609 - [User Story] Cached Privacy Policy

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::First Time Experience, defect)

Description

[Peter Dolanjski [:pdol]]

User Story:

As a user, I want to be able to access the Mozilla privacy policy while offline so that I can access this information whenever is convenient for me.


Acceptance Criteria:

1. If I access Firefox OS or Marketplace privacy policies (under Device Information>Your Privacy) while without connectivity, I can read the policy in its entirety.  
2. If I access Firefox OS or Marketplace privacy policies from the First Run Experience (under ""More about your privacy"") while without connectivity, I can read the policy in its entirety.  
3. If I access Firefox OS or Marketplace privacy policies (under Device Information>Your Privacy) while I am connected, I want the latest version of the policy to be shown (and cached) from Mozilla's website.
4. If I access Firefox OS or Marketplace privacy policies from the First Run Experience (under ""More about your privacy"") while I am connected, I want the latest version of the policy to be shown (and cached) from Mozilla's website.

Comment 1

[Candice Serran (:cserran)]

Ghislain 'Aus' Lacroix changed story state to started in Pivotal Tracker

Comment 3

[Peter Dolanjski [:pdol]]

After legal discussion, this requirement ONLY applies to Firefox OS.   We will explicitly NOT cache the privacy policy for Marketplace.

Comment 4

[Candice Serran (:cserran)]

Ghislain 'Aus' Lacroix added a comment in Pivotal Tracker:   
   
Contact Alex Fowler or Alina Hua for the latest privacy policy for FxOS.

Comment 5

[Aus Lacroix [:aus]]

IRC log of current plan for implementation:

auswerk	If I was looking for information and technical help with the CacheService, who would be a good person to talk to?
auswerk	I'm working on this — https://bugzilla.mozilla.org/show_bug.cgi?id=897609
auswerk	and the desire is to have the same presentation for the privacy policy on the web and on the device
auswerk	so, ideally, i was thinking i could pre-cache the content at build time
auswerk	and then bypass the cache validity check when no connectivity is available and simply take the cache entry and "read" it into the browser
auswerk	so that we can have *one* version of the policy
auswerk	it also means that the privacy team can continue to update the policy as they've been doing

Anyone that wants to chime in on this is more than welcome to!

Comment 6

[Aus Lacroix [:aus]]

Honza, I was hoping you could provide some feedback about the overall plan and possibly point me at the right bits to use to make it happen (if it's the right approach :)). I'm hoping to land this in the next week or two so any information you can give me now is definitely helpful.

Comment 7

[Aus Lacroix [:aus]]

A second option -- 

Use nsIWebBrowserPersist::saveDocument to cache the privacy policy and all associated assets locally at build time and refresh that data blindly when the user has connectivity. This has a lot of the same benefits, but, has one big drawback: we will cause write-outs to happen when unnecessary. Other issues with this is unnecessary network I/O.

Comment 8

[Honza Bambas (:mayhemer)]

When the platform knows it's offline from network, then cached loads (even stalled, a.k.a expired or requiring re-validation) should load from the cache unconditionally, i.e. always.

The question is whether nsIIOService knows we are w/o a functioning connection.  It can manage the online/offline status it self when manageOfflineStatus is set on it (controlled by "network.manage-offline-status" preference).  mxr tells me it's at its default value for b2g (false), i.e. no management.

Other thing (that is now missing) is a way to prevent eviction of your file (URL) from the cache.  We plan on some prioritization or pinning of cache entries.


[ Note: On the Nightly channel (gecko 27) loading stalled content from cache when offline has been broken by bug 913807 and is again fixed by bug 925352. ]

Comment 9

[Jason Smith [:jsmith]]

All targeted features for 1.3 have no plans to land for 1.3 anymore, so moving this off the tracker bug.

Comment 10

[Peter Dolanjski [:pdol]]

After further legal discussions, we have decided to put the cached privacy policy on hold for now.