| 2014-03-06 20:48:32 |
Alexandre Abreu |
description |
There are 2 ways for the webapp-container to receive a list of patterns to filter url browsing in a webapp container: through the manifest.json file that comes with a given (named) webapp, or through the command line.
At the moment, the 2 mechanisms are exclusive in the sense but not semantically equivalent. The list of url patterns in the manifest.json file is use as a mean to filter the urls that are being browsed to, but ALSO in the chromium & FF browsers to know if a webapp is to be installed/enabled when browsing in a given url.
For example, for Gmail, the hostname mail.google.com is used as a trigger to ask the user for an installation/enablement of a webapp in the browser. It is also implicitely used as a filter for browser once in the container.
The issue is that for applications like google services, the authentication mechanism is common. So when launched in the container, the user will be redirected to e.g. https://accounts.google.com or https://accounts.google.ca, etc.
So (and this is where this MR fixes it), the manifest.json cannot be modified to account for those, since we dont want to install a webapp from those URLs but we need a way to add extra navigation url patterns to allow google service webapps to be redirected to e.g. https://accounts.google.* etc. |
There are 2 ways for the webapp-container to receive a list of patterns to filter url browsing in a webapp container: through the manifest.json file that comes with a given (named) webapp, or through the command line.
At the moment, the 2 mechanisms are exclusive in the sense but not semantically equivalent. The list of url patterns in the manifest.json file is use as a mean to filter the urls that are being browsed to, but ALSO in the chromium & FF browsers to know if a webapp is to be installed/enabled when browsing in a given url.
For example, for Gmail, the hostname mail.google.com is used as a trigger to ask the user for an installation/enablement of a webapp in the browser. It is also implicitely used as a filter for browser once in the container.
The issue is that for applications like google services, the authentication mechanism is common. So when launched in the container, the user will be redirected to e.g. https://accounts.google.com or https://accounts.google.ca, etc.
So, the manifest.json cannot be modified to account for those, since we dont want to install a webapp from those URLs but we need a way to add extra navigation url patterns to allow google service webapps to be redirected to e.g. https://accounts.google.* etc. |
|
