This bug was fixed in the package oxide-qt - 1.5.3-0ubuntu2
---------------
oxide-qt (1.5.3-0ubuntu2) vivid; urgency=medium
* 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
-- Chris Coulson <chris.coul...@canonical.com> Wed, 28 Jan 2015 14:08:55
+0000
** Changed in: oxide-qt (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1249387
Title:
hook Oxide into Ubuntu platform API for media-hub
Status in the base for Ubuntu mobile products:
In Progress
Status in Media Hub:
Fix Committed
Status in Oxide Webview:
Fix Committed
Status in oxide-qt package in Ubuntu:
Fix Released
Bug description:
Right now oxide uses software rendering for audio and video via the
chromium content api ffmpeg implementation for libffmpegsumo.so. This
is provided in either oxideqt-codecs (suitable for main) or oxideqt-
codecs-extra (suitable for universe). oxideqt-codecs-extra includes
mp3 and h264 playback. Software rendering is not ideal on the phone,
but in addition to that, webbrowser-app, webapp-container and apps
using Oxide or UbuntuWebView are subject to application lifecycle and
therefore the user experience for things such as grooveshark playlists
and youtube videos is poor because the device will shut off the screen
or suspend during playback.
The correct way to solve this is for Oxide to use the media-hub in
some manner. This was somewhat easily solved with QtWebKit since it
used gstreamer and it could be made to hook into the media-hub.
However, QtWebKit is dead upstream which is one reason why we are
using Oxide. We should look to see how qtwebengine is handling this
(ie, are they just using the software rendering or are they redoing
the QtWebKit gstreamer work for qtwebengine). Perhaps we could provide
our own libffmpegsumo.so or wrap it in some manner. Perhaps we can
work with upstream to have something that works better on Linux/Ubuntu
in general. Whatever method is chosen should be maintainable in the
face of weekly or biweekly stable updates (low api churn) and 6-8 week
beta updates (potential api churn) to the chromium content api, since
we expect this update frequency in our stable releases for security,
bug and web compatibility fixes over a period of up to 5 years.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1249387/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
