Comment 10 for bug 1036726

Le 18/10/2013 20:24, Robert Bruce Park a écrit :
> My understanding at this point is that we are working towards running
> webapps in an isolated webapps container, ie, neither firefox nor
> chromium, but instead our own webbrowser-app (which is a very
> lightweight webkit browser spawned from the Ubuntu Touch project).
>
> The goal of doing it this way is that it will allow us to drop a large
> amount of hard-to-maintain code from unity-firefox-extension and unity-
> chromium-extension, and provide for a smoother overall experience (eg,
> chromeless windows for webapps to run in, better/easier integration with
> the Unity launcher/switcher/etc).
This is indeed the plan.

Yet, I understand the use-case and the solution may be in how we bind
online accounts to dedicated webapp container instances.

If you enable the new container mode, you will get a dedicated browser
instance per webapp. Each instance has its own set of
cookie/password/history databases. So you should be able to read
professional emails when logged as user A, and still be able to read
news (or other emails) when logged as user B, without having to use 2 or
3 different browsers.

To enable the new container mode, do:

apt-get install webbrowser-app
touch ~/.local/share/unity-webapps/enable-webapp-container

You will have to re-create your .desktop shortcuts, as the new mode
requires an extra property in it (the StartupWMClass paramater).

Then, each webapp will run in its own browser container.

To get back to using the default browser, just remove the configuration
file.

David