[FFE] Webapps support for the new Oxide container
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| WebApps: libunity-webapps |
Fix Released
|
Undecided
|
Unassigned | ||
| unity-webapps-qml |
Fix Released
|
Undecided
|
Unassigned | ||
| libunity-webapps (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| oxide-qt (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| unity-webapps-qml (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| webbrowser-app (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
This is a feature freeze exception request to integrate the following feature in the upcoming Ubuntu 14.04 release.
The overall web application support in Ubuntu currently relies on various components and a web container(s) in particular. So far we have been using Firefox and Chromium, by way of browser extensions, to detect, host and integrate web applications in Ubuntu.
On mobile devices however, we have already switched to using our own webapp container, based on webbrowser-app.
The integration itself has been present as an option since 13.10. However we have been using the QtWebkit engine so far.
This request is to also enable and use our webapp-container by defaullt, with the Oxide engine, on the desktop edition.
The change impacts a set of packages linked to this bug report.
NOTE: This request is not complete and serves to let the release team know of the impact and scope of changes, while the individual MPs with fixes are being consolidated. It will be updated at the beginning of next week when the landing silo is ready for a potential landing.
Related branches
- PS Jenkins bot (community): Approve (continuous-integration)
- WebApps: Pending requested
-
Diff: 384 lines (+191/-65)6 files modifieddebian/control (+1/-0)
src/Ubuntu/UnityWebApps/UnityWebApps.js (+10/-12)
src/Ubuntu/UnityWebApps/UnityWebAppsUtils.js (+127/-45)
src/Ubuntu/UnityWebApps/common/js/unity-backend-messaging-proxy.js (+43/-0)
src/Ubuntu/UnityWebApps/common/js/unity-binding-bridge.js (+5/-6)
src/Ubuntu/UnityWebApps/unity-webapps-api.js.in (+5/-2)
| tags: | added: oxide |
| description: | updated |
| Jamie Strandboge (jdstrand) wrote | #1 |
| Adam Conrad (adconrad) wrote | #2 |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in unity-webapps-qml (Ubuntu): | |
| status: | New → Fix Released |
| Changed in unity-webapps-qml: | |
| status: | New → Fix Released |
| Changed in libunity-webapps (Ubuntu): | |
| status: | New → Fix Released |
| Changed in libunity-webapps: | |
| status: | New → Fix Released |
| Changed in oxide-qt (Ubuntu): | |
| status: | New → Invalid |
| Changed in webbrowser-app (Ubuntu): | |
| status: | New → Invalid |
MIR request for Oxide gives some background: bug #1293681. Essentially, Oxide "is the Chromium Content API wrapped with bindings for Ubuntu. The Chromium Content API contains Blink, V8, etc and is subject to main new security vulnerabilities. The Oxide bindings are written in such a way that we are able to pull new upstream Chromium Content API versions without changing the Oxide API, offering us the ability to track upstream Chromium for security fixes." Oxide is the solution for providing security support to the webapp container for the LTS and we really cannot use webapp-container without it.