Public bug reported:
In my opinion the webapp-container needs show the progression and the
addressbar. Showing a non-editable addressbar will help the users to know in
which url they are and will keep users safe.
Ex : a user can click on a phishing url from an email that will bring him to a
fak
Public bug reported:
QtWebkit is used as a fallback to Oxide renderer and the switch between
the 2 is at runtime based on various bits (flag or runtime conditions).
More memory than necessary is used in the "regular" context (oxide as
backend) for 14.04 webapps since the qtwebkit libs are loaded a
I can’t reproduce this issue anymore with the latest image. Either a
recent change in oxide fixed it, or it was fixed in gmail itself.
** Changed in: webbrowser-app
Status: Confirmed => Fix Released
** Changed in: webbrowser-app
Assignee: Olivier Tilloy (osomon) => (unassigned)
--
Y
Per Chris, oxide is stating that it is using all the codecs when using
the oxideqt-codecs package rather than just the subset. Chromium is
written in a matter that hardcodes this list such that all of oxide
needs to be built twice rather than just ffmpeg. This can be solved in
packaging.
The webap
This bug was fixed in the package webbrowser-app -
0.23+14.04.20140409-0ubuntu1
---
webbrowser-app (0.23+14.04.20140409-0ubuntu1) trusty; urgency=low
[ Alexandre Abreu ]
* Add support for Oxide's onNavigationRequested in the container (LP:
#1302769)
* Webapps: maintain the s
5 matches
Mail list logo