lp://qastaging/ubuntu/trusty/webbrowser-app

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

54. By PS Jenkins bot on 2014-04-14

[ Olivier Tilloy ]
Force the page title to be reset to an empty string when the
activity view is being hidden. (LP: #1307420)

53. By PS Jenkins bot on 2014-04-11

[ Michael Sheldon ]
* Add support for file upload via content-hub

[ Ugo Riboni ]
* Add support for file upload via content-hub

[ Alexandre Abreu ]
* Make sure that we dont load unecessary libs (oxide or qtwebkit)
  correspnding to the webengine that we dont use. (LP: #1306037)
* Add a basic set of integration tests for the webapp container

[ Ubuntu daily release ]
* New rebuild forced

[ Olivier Tilloy ]
* Enable UA overrides for all form factors, each in a separate file.
  Add an override for google calendar on desktop. Clean up the
  construction of the default UA string for easier reading and
  maintenance.

[ Bill Filler ]
* Add support for file upload via content-hub

52. By PS Jenkins bot on 2014-04-10

[ David Barth ]
To prevent https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
toolkit/+bug/1305834 caused by a recent UI toolkit change, we are
returning an empty title for now. (LP: #1305834)

51. By PS Jenkins bot on 2014-04-09

[ Alexandre Abreu ]
* Add support for Oxide's onNavigationRequested in the container (LP:
  #1302769)
* Webapps: maintain the session cookies for the user session Instruct
  Oxide to store/load the session cookies on disk in a per-webapp
  directory under XDG_RUNTIME_DIR. The first time in a user session
  that the webapp is launched, the session cookies (leftover from
  previous sessions) are not loaded, but only stored (this is the
  chrome's "persistent" sessionCookieMode). The next times, session
  cookies are both loaded and stored (chrome's "restored"
  sessionCookieMode).

[ Alberto Mardegan ]
* Webapps: maintain the session cookies for the user session Instruct
  Oxide to store/load the session cookies on disk in a per-webapp
  directory under XDG_RUNTIME_DIR. The first time in a user session
  that the webapp is launched, the session cookies (leftover from
  previous sessions) are not loaded, but only stored (this is the
  chrome's "persistent" sessionCookieMode). The next times, session
  cookies are both loaded and stored (chrome's "restored"
  sessionCookieMode).

50. By PS Jenkins bot on 2014-04-07

[ Ubuntu daily release ]
* New rebuild forced

[ Olivier Tilloy ]
* Update to oxide 1.0.

49. By PS Jenkins bot on 2014-04-03

[ Olivier Tilloy ]
Re-enable javascript dialogs, now that they are available in oxide.

48. By PS Jenkins bot on 2014-04-02

[ CI bot ]
* Resync trunk

[ Alexandre Abreu ]
* Small update to the --webapp flag documentation

[ Olivier Tilloy ]
* Null-check to fix a segmentation fault when --help is passed to the
  executable.

47. By PS Jenkins bot on 2014-03-28

[ Olivier Tilloy ]
Land the master Oxide support branch. See individual revisions for
details. (LP: #1271756)

46. By PS Jenkins bot on 2014-03-24

[ Alexandre Abreu ]
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 that from the webapp-container's perspective
it only considers one or another when filtering navigation (the
webapp manifest one being preferred) but they are 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. We provide here
2 things: an way for the url patterns passed down from the command
line to be also considered in the navigation filtering,. a way to
simplify url patterns for google apps (LP: #1288982)

45. By PS Jenkins bot on 2014-03-19

[ Olivier Tilloy ]
Use the renderer only once when rendering a thumbnail. This seems to
fix the crash that was happening at destruction time. (LP: #1294219)