dx-packages team mailing list archive

Thread
Date

[Bug 1288889] Re: When using the runner as a dispatcher, no mechanism to fix a webapp from "leaking" into the browser from the container

To: dx-packages@xxxxxxxxxxxxxxxxxxx
From: David Barth <david.barth@xxxxxxxxxxxxx>
Date: Tue, 18 Mar 2014 16:50:12 -0000
Reply-to: Bug 1288889 <1288889@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Verified to work in a silo build with the linked merge proposal.

** Changed in: libunity-webapps
       Status: New => Fix Committed

** Changed in: libunity-webapps (Ubuntu)
       Status: New => Fix Committed

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity-webapps in Ubuntu.
https://bugs.launchpad.net/bugs/1288889

Title:
  When using the runner as a dispatcher, no mechanism to fix a webapp
  from "leaking" into the browser from the container

Status in WebApps: libunity:
  Fix Committed
Status in “libunity-webapps” package in Ubuntu:
  Fix Committed

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.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity-webapps/+bug/1288889/+subscriptions