oxide-qt 1.2.5-0ubuntu0.14.04.1 source package in Ubuntu

Changelog

oxide-qt (1.2.5-0ubuntu0.14.04.1) trusty-security; urgency=medium

  * Update to v1.2.5
    - see USN-2345-1
    - Bump Chromium rev to 38.0.2125.101
    - Fix LP: #1347924 - QProcess::waitForFinished() hangs - stop using
      ContentMainRunner for starting the browser code - it does things with
      process global state that are unexpected in a public library (eg,
      setting the SIGCHLD handler to the default which breaks QProcess because
      it relies on its own custom handler). We do still set the SIGPIPE action
      to SIG_IGN, but only if it is SIG_DFL when we start. We also abort if the
      SIGCHLD action is SIG_IGN when we initialize
    - Fix LP: #1214034:
      + Add API's to query the security status of the webview
        (WebView.securityStatus property + SecurityStatus and SslCertificate
        classes)
      + Add WebView.certificateError signal and CertificateError class to
        give the application a chance to allow certain SSL errors (some errors
        are non-overridable and this is enforced by Oxide - in which case, the
        signal only acts as a notification)
      + Add WebView.blockedContent property, which is a bitmask of content
        types that have currently been blocked - currently this only indicates
        MixedDisplay and MixedScript, but will be extended later on for other
        content types (eg, cookies, popups etc)
      + Add WebView.setCanTemporarily{Display,Run}InsecureContent functions,
        which allows the mixed content blocker preferences to be overridden
        temporarily (will reset on navigation to a new page)
    - Fix LP: #1224707 - Use a localized Accept-Language header
    - Make certificate revocation checking work properly, which is also
      required for EV to work. Also fixes some console spew (LP: #1240723)
    - Fix LP: #1285750 - Add support for building a chromedriver binary
    - Fix LP: #1286204 - Make double-tap-to-zoom work
    - Fix LP: #1361868 - Don't leak GeolocationPermissionRequest if there are
      no handlers on WebView.geolocationPermissionRequested
    - Add WebContext.cookieManager API
    - Fix LP: #1260048 - Don't initialize NSS with a user DB for now
    - Fix LP: #1371166 - Geolocation fails when the location source returns
      invalid values for some attributes
    - Fix LP: #1362543 - Web application fails to load properly every other
      time. Ensure that when a new cache is created, the initial cache stats
      are stored to permanent storage immediately to avoid the cache being
      left in an inconsistent state if the process exits uncleanly before
      the stats are updated
 -- Chris Coulson <email address hidden>   Thu, 11 Sep 2014 11:33:02 +0100