On Tue, Aug 5, 2014 at 11:27 PM, Jonas Sicking <[email protected]> wrote:
> On Tue, Aug 5, 2014 at 7:51 PM, James Burke <[email protected]> wrote: > > The use case is a site that has app-like functionality for offline, but > has > > product pages that are not tied to that app, and the app does not know > how > > to navigate to them on its own. And both the app and the site are from > the > > same domain, because that is the well known identifier for users. > > Sorry, I don't understand this. > > This was the example I was thinking of, perhaps I have a misunderstanding somewhere: My users knows about my password manager, at pwm.com. I have the following structure: * pwm.com/ - index page that gives summary, and an install button. * pwm.com/app.html the main app page mentioned in the manifest, the launch_path. It uses appcache or a way to get local assets under /app as the installed app. Then a bunch of product pages that are not really needed for use of the app once it is installed: * pwm.com/features.html - in depth feature survey. * pwm.com/help.html - could be a help forum/support that changes often. * pwm.com/comparison.html - compares against similar password managers. I would prefer to not have those last three open inside my app, as the app was configured around local data storage and may have routes/pages that do not correspond with the public site URLs. So a way to tell the system “do not open up my app for those URLs, just what is installed locally”. Perhaps similar to when I have a tab opened for pwm.com/app.html in a desktop browser, then in another tab I am on a different web site and I click on a link on that site that goes to pwm.com/help.html. James
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
