Closed Bug 937698 Opened 11 years ago Closed 11 years ago

Add :offline to potatosearch

Categories

(Marketplace Graveyard :: Search, enhancement, P2)

enhancement

Tracking

(Not tracked)

VERIFIED FIXED
2013-12-03

People

(Reporter: clouserw, Assigned: cvan)

References

Details

A request from the mailing list (https://groups.google.com/forum/#!msg/mozilla.dev.marketplace/BRrCZtgjeZY/FsmfsBS5A7UJ ) to add :offline support to PotatoSearch. Is this a simple addition?
I swear there's another bug for this. But sure. If we do this based on presence of `appcache_path` in the manifest OR if the app is a packaged app, this is easy. If we're doing it based on presence of appcache in the HTML, valid appcache manifest, presence of serviceworkers, etc. then that's a bit complicated and we'll need some Basta love up in here.
Assignee: nobody → cvan
Priority: -- → P2
(In reply to Christopher Van Wiemeersch [:cvan] from comment #1) > I swear there's another bug for this. But sure. > > If we do this based on presence of `appcache_path` in the manifest OR if the > app is a packaged app, this is easy. If we're doing it based on presence of > appcache in the HTML, valid appcache manifest, presence of serviceworkers, > etc. then that's a bit complicated and we'll need some Basta love up in here. An app without appcache in its manifest is not an "offline capable" app in the strict sense of the word (the platform will not precache on install), so let's not treat it as such. If the devs add it to the HTML but not the manifest, that's a bug.
(In reply to Fred Wenzel [:wenzel] from comment #3) > (In reply to Christopher Van Wiemeersch [:cvan] from comment #1) > > I swear there's another bug for this. But sure. > > > > If we do this based on presence of `appcache_path` in the manifest OR if the > > app is a packaged app, this is easy. If we're doing it based on presence of > > appcache in the HTML, valid appcache manifest, presence of serviceworkers, > > etc. then that's a bit complicated and we'll need some Basta love up in here. > > An app without appcache in its manifest is not an "offline capable" app in > the strict sense of the word (the platform will not precache on install), so > let's not treat it as such. If the devs add it to the HTML but not the > manifest, that's a bug. Just to clarify: are you suggesting that a packaged app is not an offline app or an app that uses serviceworkers? Also, just because an app has an `appcache_path` and manifest doesn't mean that it degrades gracefully offline (but that an attempt was made and at least some resources are available offline).
(In reply to Christopher Van Wiemeersch [:cvan] from comment #4) > Just to clarify: are you suggesting that a packaged app is not an offline > app or an app that uses serviceworkers? Also, just because an app has an > `appcache_path` and manifest doesn't mean that it degrades gracefully > offline (but that an attempt was made and at least some resources are > available offline). Good points. Sorry for being ambiguous. I was talking about hosted apps whose manifest does not define an appcache path. In that case, it should not be treated as offline-capable. For now, I'm suggesting "If we do this based on presence of `appcache_path` in the manifest OR if the app is a packaged app, this is easy." is the right approach, while keeping in mind this is not a perfect representation of a good offline experience.
Agree 100%. We just ought to be clear that we don't falsely advertise "works 100% offline." But this will be good :)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-12-03
Verified as fixed.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.