[FFE] oxide 1.5

[Olivier Tilloy]

This is a feature freeze exception request for oxide 1.5.3. The archive currently has 1.4.2-0ubuntu2.

Oxide 1.5.3 is based on branch 41 of chromium (41.0.2272.53), soon to become the stable branch (within a couple of weeks at most IIRC). As such it includes a number of enhancements and security fixes from upstream chromium.
It also includes a number of fixes in oxide itself as well as a new API to let embedders delegate positioning of the chrome to oxide (bug #1370366).

Full changelog:

* Update to v1.5.3
    - Bump Chromium rev to 41.0.2272.53
    - Fix LP: #1402975 - set a minimum viewport width of 980px on mobile
      for sites that don't specify a viewport width. Fixes layout of some
      desktop sites, and matches the behaviour of Chrome on Android
    - Fix LP: #1412981 - Geolocation permission requests from subframes are
      not cancelled if the frame is deleted or navigated to another site
    - Fix LP: #1379776 - Spoof Android for the purposes of GPU feature
      blacklisting on the phone. This means accelerated 2d canvas is now
      enabled on all devices that Chrome enables it on (including the Nexus 4),
      and other GPU features (eg, GPU rasterization) are enabled on devices
      where Chrome supports it
    - Fix LP: #1370366 - Add LocationBarController API, which allows the
      renderer compositor to calculate the position of the browser top header.
      This enables the header to be animated in sync with the content on
      scrolling
    - Fix LP: #1408136 - Committed LoadEvents fire for subframe loads when
      they shouldn't
    - Fix LP: #1377198 - CertificateError is not cancelled if you stop the
      pending navigation
    - Fix LP: #1373383 - The video player on Youtube does not resize correctly
      when transitioning from landscape to portrait. Ensure we correctly
      update the screen geometry and orientation visible to web content when
      the device orientation changes, and turn on orientation events
    - Really fix LP: #1337506 - Abort with
      "FATAL:texture_manager.cc(76)] Check failed: texture_count_ == 0u (1 vs. 0)"
      on shutdown
    - Fix LP: #1398044 - Fails to build with Qt 5.4
    - Fix LP: #1249387 - Add experimental support for playing audio through
      mediahub with the HTML media elements (Off by default. Video and
      MediaSource are not yet implemented. Not built yet because it depends
      on packages in universe)
    - Fix LP: #1417042 - Remove inactive touch points from the current touch
      state when we process a new touch event
    - Fix LP: #1417963 - Adapt to behaviour change in handling of QVariants
      from QML to C++ in Qt 5.4
    - Update the form factor detection code to not rely on the EGL vendor for
      detecting that we're on a device - use the Android system properties
      instead
    - Tidy up WebContents ownership during unload by adding a new singleton
      responsible for handling unloading (WebContentsUnloader)
    - Refactor WebFrame to be based around RenderFrameHost rather than
      FrameTreeNode, which we aren't meant to be using
    - Call QDesktopServices::openUrl on the UI thread. Failures are no longer
      propagated back to the resource dispatcher, so all attempts to open a
      URL externally will result in the load being cancelled whether there
      is an external handler or not
  * Update debian/control to add extra build dependencies:
    - libandroid-properties-dev on armhf, used for gathering data for GPU
      feature blacklisting when running on the phone
  * Update debian/liboxideqtcore0.install to install V8 snapshot data
  * Drop oxideqmlscene - this was only necessary when qmlscene didn't support
    setting up a shared GL context

Oxide 1.5.3 has been extensively tested in the past couple of weeks by David Barth, Alexandre Abreu, Chris Coulson and myself, on desktop and various mobile devices, including Nexus 4, Nexus 7 and BQ Aquaris E4.5.

Packages are available in the phablet-team PPA for testing: https://launchpad.net/~phablet-team/+archive/ubuntu/ppa/+sourcepub/4789477/+listing-archive-extra.

[Jamie Strandboge (jdstrand)]

From IRC discussion:
10:31 < jdstrand> can someone take a look at the oxide 1.5 FFe? (bug #1425599)
10:31 < ubot93> bug 1425599 in oxide-qt (Ubuntu) "[FFE] oxide 1.5" [Undecided,New] https://launchpad.net/bugs/1425599
10:31 < jdstrand> oSoMoN and chrisccoulson can speak to the actual changes
10:33 < jdstrand> but oxide is in a weird area wrt to this FFe. we plan to push this to stable releases because it is a security update. however, there are some features in it that are for important phone bugs
10:34 < jdstrand> in other words, oxide was specifically created to address security issues, fix bugs and implement features to enhance the phone (ie, it uses the firefox model), yet it is blocked on FFe
10:34 < jdstrand> seems we wouldn't block firefox-- we would just upload it
10:37 < jdstrand> I'm not sure that it helps, but we discussed that we will pursue an MRE for oxide after vivid releases since it is a lot like firefox, and firefox has one
10:44 < ogra_> why does it need an FFe at all ?
10:44 < ogra_> given it is a rolling package across all releases anyway
10:54 < jdstrand> ogra_: right
10:55 < jdstrand> I'm not sure why oSoMoN was advised to file one
10:55 < jdstrand> I think sil2100 may have requested it, but not sure where this was discussed in terms of formal processes (if at all)
10:56 < oSoMoN> Mirv initially told me I’d need to file an FFe
10:57 < sil2100> I wasn't aware of any exceptions, so FFe was the safest bet - and if someone from the release team would comment that we don't need those, well, we wouldn't request it anymore ;)
10:57 < sil2100> I understand all the rationale, it's just that since it's a release-team decision I wanted to have some confirmation from their side
10:58 < ogra_> sil2100, well, browsers are generally rolling anyway
11:01 < jdstrand> right, well, the argument is out there for the release team to comment. we'll pursue a MRE to kinda cement the idea for stable releases
12:07 < infinity> jdstrand: I take it as a given that firefox, chromium, and oxide don't require FFes

[Jamie Strandboge (jdstrand)]

Unsubscribing the release team based on irc feedback. FFe not required for oxide.

[Jamie Strandboge (jdstrand)]

Oh heh, actually I can't do that :P

Marking as Invalid since the FFe isn't needed.