[Ubuntu-webapps-bugs] [Bug 1302769] Re: Popup windows not working

2014-04-10 Thread Launchpad Bug Tracker
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 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).
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Wed, 09 Apr 2014 
13:34:57 +

** Changed in: webbrowser-app (Ubuntu)
   Status: In Progress = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to webbrowser-app.
https://bugs.launchpad.net/bugs/1302769

Title:
  Popup windows not working

Status in Unity integration for GMail:
  In Progress
Status in Web Browser App:
  In Progress
Status in “webbrowser-app” package in Ubuntu:
  Fix Released

Bug description:
  Gmail has an option to view the message in a separate window. Using
  this option causes the main window to be replaced with a blank screen,
  and the window itself is maximized.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-webapps-gmail/+bug/1302769/+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


[Ubuntu-webapps-bugs] [Bug 1305317] Re: Youtube webapp reads fewer videos with the new oxideqt-codecs package

2014-04-10 Thread Jamie Strandboge
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 webapps team said this need to be fixed before 14.04 release.

** Summary changed:

- Youtube webapp reads less videos with the new oxideqt-codecs package
+ Youtube webapp reads fewer videos with the new oxideqt-codecs package

** Also affects: oxide-qt (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: oxide-qt (Ubuntu)
   Importance: Undecided = High

** Changed in: oxide-qt (Ubuntu)
Milestone: None = ubuntu-14.04

** Changed in: oxide-qt (Ubuntu)
   Status: New = Triaged

-- 
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/1305317

Title:
  Youtube webapp reads fewer videos with the new oxideqt-codecs package

Status in Oxide Webview:
  New
Status in “oxide-qt” package in Ubuntu:
  Triaged

Bug description:
  The new build which enables oxideqt-codecs and oxideqt-codecs-extra
  has an impact on the youtube dekstop webapp to play certain videos.

  Previously, ie without any of the codec packages, youtube was able to
  play certain videos. Now instead we receive an 'undefined' message
  from youtube.

  If installing the oxideqt-codecs-extra package, the video plays again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1305317/+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


[Ubuntu-webapps-bugs] [Bug 1297951] Re: flicking in gmail causes incorrect behavior

2014-04-10 Thread Olivier Tilloy
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)

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to webbrowser-app.
https://bugs.launchpad.net/bugs/1297951

Title:
  flicking in gmail causes incorrect behavior

Status in Web Browser App:
  Fix Released

Bug description:
  using oxide from universe: 1.0.0~bzr437-0ubuntu1
  and webbrowser-app from phablet-team ppa: 
0.23+14.04.20140324-0ubuntu1~withoxide2

  gmail is now rendered correctly as we're using the override string
  found here /usr/lib/arm-linux-
  gnueabihf/qt5/qml/Ubuntu/Components/Extras/Browser/ua-override-
  worker.js.

  This override basically adds the Safari token.

  The problem is flicking the messages view to scroll typically results
  in inadvertently opening the message that is below where you release
  your finger. Appears the sensitivity is too high and somehow a pressed
  event is occuring. This only seems to occur on gmail (tested and this
  does not happen on twitter, g+, facebook). I've also found that
  removing Safari from the override makes this problem go away, but
  introduces another problem previously reported where a message can
  never be opened. I tested various override permutations but couldn't
  get it to work correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webbrowser-app/+bug/1297951/+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


[Ubuntu-webapps-bugs] [Bug 1306037] [NEW] [webapp-container] Do not load qtwebkit libs (used as fallback) when they are not needed

2014-04-10 Thread Alexandre Abreu
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 anyway
given the way that the qml is layedout.

** Affects: webbrowser-app
 Importance: Medium
 Assignee: Alexandre Abreu (abreu-alexandre)
 Status: Triaged

** Changed in: webbrowser-app
 Assignee: (unassigned) = Alexandre Abreu (abreu-alexandre)

** Changed in: webbrowser-app
   Importance: Undecided = Medium

** Changed in: webbrowser-app
   Status: New = Triaged

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to webbrowser-app.
https://bugs.launchpad.net/bugs/1306037

Title:
  [webapp-container] Do not load qtwebkit libs (used as fallback) when
  they are not needed

Status in Web Browser App:
  Triaged

Bug description:
  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 anyway given the way that the qml is layedout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webbrowser-app/+bug/1306037/+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


[Ubuntu-webapps-bugs] [Bug 1306274] [NEW] [webapp-container] needs to show more infos by default

2014-04-10 Thread Adnane Belmadiaf
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 
fake facebook/twitter/etc.. login page, so without showing the url it's hard to 
guess that without seeing the url and if the page is encrypted (bug 1236364), 
and it's boring to wait for something that you don't know its progression.

i think this should be marked as Critical and should be fixed ASAP.

** Affects: webbrowser-app
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to webbrowser-app.
https://bugs.launchpad.net/bugs/1306274

Title:
  [webapp-container] needs to show more infos by default

Status in Web Browser App:
  New

Bug description:
  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 fake facebook/twitter/etc.. login page, so without showing the url it's hard 
to guess that without seeing the url and if the page is encrypted (bug 
1236364), and it's boring to wait for something that you don't know its 
progression.

  i think this should be marked as Critical and should be fixed ASAP.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webbrowser-app/+bug/1306274/+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