Value type enums are not exposed to QML with Qt5.5

[Olivier Tilloy]

When launching webbrowser-app in a clean and up-to-date xenial desktop VM, I’m seeing the following messages in the console:

file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/UbuntuWebView02.qml:142: TypeError: Cannot read property 'TypeFailed' of undefined
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/UbuntuWebView02.qml:141: TypeError: Cannot read property 'TypeStopped' of undefined
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/UbuntuWebView02.qml:140: TypeError: Cannot read property 'TypeSucceeded' of undefined
file:///usr/share/webbrowser-app/webbrowser/Browser.qml:1196: TypeError: Cannot read property 'TypeCommitted' of undefined
file:///usr/share/webbrowser-app/ChromeController.qml:78: TypeError: Cannot read property 'TypeStarted' of undefined

(I’m seeing multiple instances of each message)

oxide version 1.11.3-0ubuntu3 is installed

[Olivier Tilloy (osomon)]

Note that the browser seems to otherwise work well, but as expected because of these errors the history database is not being populated.

[Olivier Tilloy (osomon)]

I’m not seeing that error with the same version of oxide (1.11.3-0ubuntu0.15.10.1) on wily.

[Olivier Tilloy (osomon)]

It appears that types that inherit QQmlValueType are not exposed any longer with Qt 5.5.
This can be observed with this simple piece of QML code:

  import QtQuick 2.4
  import com.canonical.Oxide 1.11 as Oxide
  Item {
    Component.onCompleted: {
      console.log(Oxide.SecurityStatus) // is a QObject, prints "[object Object]"
      console.log(Oxide.SecurityStatus.SecurityLevelError) // prints "4"
      console.log(Oxide.LoadEvent) // is a QQmlValueType, prints "undefined"
      console.log(Oxide.SslCertificate) // is a QQmlValueType, prints "undefined"
    }
  }

[Olivier Tilloy (osomon)]

Duplicate of bug #1488364 ?

[Chris Coulson (chrisccoulson)]

It's not a duplicate - this is a separate issue. I've updated the title accordingly

[Chris Coulson (chrisccoulson)]

Basically, we need some calls to qmlRegisterValueTypeEnums in OxideQmlPlugin::registerTypes

[Chris Coulson (chrisccoulson)]

This is fixed with http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/revision/1306. I've done a build against the xenial stack and ran the full set of unit tests - they all pass with the exception of the tests in tst_SslCertificate.qml that rely on SslCertificate.issuer (due to bug 1488364)

[Chris Coulson (chrisccoulson)]

Might do a xenial only 1.11.5 for this

[Launchpad Janitor (janitor)]

This bug was fixed in the package oxide-qt - 1.11.5-0ubuntu1

---------------
oxide-qt (1.11.5-0ubuntu1) xenial; urgency=medium

  * Update to v1.11.5
    - Fix LP: #1532135 - Ensure enums for value types are actually exposed to
      QML when building with Qt5.5

 -- Chris Coulson <email address hidden> Mon, 11 Jan 2016 17:11:11 +0000