[Web apps] that use OA just close if there is no existing account and no connection

[Brendan Donegan]

Prerequisites:

There must be NO account created for the web app in question (steps assume Facebook). Connectivity should have been disabled (flight mode on and make sure wifi is disabled too)

Steps to reproduce:

1. Open the Facebook web app from the click scope
2. Wait a few seconds

Expected result:

There is some obvious feedback as to what happened (need a connection to create an account but don't have one)

Actual result:

The application just closes

ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: webapp-container 0.23+14.10.20141008-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu5
Architecture: armhf
Date: Thu Oct 16 12:55:46 2014
InstallationDate: Installed on 2014-10-16 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328)
SourcePackage: webbrowser-app
UpgradeStatus: No upgrade log present (probably fresh install)

-- UX Solution --
When Internet connection is unavailable, the web app OA landing page will be displayed
https://docs.google.com/a/canonical.com/presentation/d/1IpCWtWuGPES5llwmoscawhn2IG4fxOggMO8F_RM_zms/edit#slide=id.g41b9f425c_4_84

[Matthew Paul Thomas (mpt)]

Brendan/David, can you explain why this problem is specific to OA? In other words, how is the case of a Web app that uses OA different from the case of a Web app that doesn't use OA?

No app should close merely because it can't access the Internet. But for a Web app, I guess you might see nothing except an empty screen with the text "Connect to the Internet to use {name of app}.", with the app auto-reloading when it's focused with an Internet connection. That error text shouldn't have any buttons or anything for connecting to the Internet, because those would already be in the dialog for bug 1275761 appearing on top of it.

[Matthew Paul Thomas (mpt)]

<brendand> mpt, in the case where there is no connection

<brendand> mpt, a web app that doesn't use OA shows the standard 'no connection' browser page
<brendand> mpt, one that does briefly flashes up the OA UI then closes

So, while I'm not Giorgio, I expect the design will be simply for an OA-using app to stay open like a non-OA-using one does.

[Giorgio Venturi (giorgio-venturi-deactivatedaccount)]

The best solution would be for the webapp to be able to provide a custom page for the standard 500 errors page with the app branding and an indication that Internet Connection is required.

Well designed webapps should work in general without an Internet Connection.