ubuntu-webapps-bugs team mailing list archive

[Launchpad Bug Tracker <1322622@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package webbrowser-app -
0.23+14.10.20140709-0ubuntu1

---------------
webbrowser-app (0.23+14.10.20140709-0ubuntu1) utopic; urgency=low

  [ Michael Sheldon ]
  * Add support for downloads via content-hub on non-desktop devices
    when it's either not possible to render a file within the browser
    itself or when a download is explicitly requested via the Content-
    Disposition header. (LP: #1198347)

  [ Olivier Tilloy ]
  * Remove a workaround for bug #1322622 that has been properly fixed in
    oxide. (LP: #1322622)
  * Re-enable the favicon support now that oxide supports it. (LP:
    #1259216)
 -- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx>   Wed, 09 Jul 2014 16:37:04 +0000

** Changed in: webbrowser-app (Ubuntu)
       Status: New => 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/1322622

Title:
  No rendering happens on a dynamically instantiated webview if its
  'visible' property was changed

Status in Oxide Webview:
  Fix Released
Status in Oxide 1.0 series:
  Fix Released
Status in “webbrowser-app” package in Ubuntu:
  Fix Released

Bug description:
  Dynamically instantiating a webview in QML (using
  component.createObject(…)) without initially loading a URL, and
  ensuring it’s initially invisible then shown, and later loading a URL,
  results in no rendering. This can be worked around by then changing
  the 'visible' property to false and then true again.

  I’m attaching a small example that reproduces the issue. Note that it
  replicates webbrowser-app’s behaviour to deal with tabs, so it’s a
  pretty critical issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1322622/+subscriptions