When using the runner as a dispatcher, no mechanism to fix a webapp from "leaking" into the browser from the container
Bug #1288889 reported by
Alexandre Abreu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| WebApps: libunity-webapps |
Fix Committed
|
Undecided
|
Unassigned | ||
| libunity-webapps (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
When a webapp is being run in the container, there is no mechanism to specify a list of url extra patterns specific to the container so that it doesn't leak into the browser for certain cases.
It happens for e.g. google apps that redirect to a non webapp specific uri for account auth.
Those url patterns should be distinct from the ones in the webapps's manifest "include" spec since they are specific to the container and should not be taken into account when matching from the webbrowser (chromium, ff etc.)
Related branches
lp:~abreu-alexandre/libunity-webapps/allow-patterns-to-be-passed-down-to-container
- David Barth (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 81 lines (+34/-4)1 file modifiedsrc/runner/unity-webapps-runner.c (+34/-4)
Revision history for this message
| David Barth (dbarth) wrote | #1 |
| Changed in libunity-webapps: | |
| status: | New → Fix Committed |
| Changed in libunity-webapps (Ubuntu): | |
| status: | New → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in libunity-webapps (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Verified to work in a silo build with the linked merge proposal.