dx-packages team mailing list archive

[Launchpad Bug Tracker <1288889@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package libunity-webapps -
2.5.0~+14.04.20140317.1-0ubuntu1

---------------
libunity-webapps (2.5.0~+14.04.20140317.1-0ubuntu1) trusty; urgency=low

  [ CI bot ]
  * Resync trunk

  [ Alexandre Abreu ]
  * Allow URL patterns to be passed down to the container for proper
    navigation URL filtering (LP: #1288889)
  * Reenable container flag to allow one to test the container
 -- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx>   Mon, 17 Mar 2014 21:36:12 +0000

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

-- 
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 Released

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