I agree, some automated tests to catch potential problems similar to
that one upfront would be very useful. Let’s keep this bug open to track
the addition of such tests, although I’m not sure what those tests would
look like yet.
** Summary changed:
- Ubuntu.Web QML component not providing stable versioned API
+ Add automated tests to prevent API breakage for Ubuntu.Web
** Changed in: webbrowser-app (Ubuntu)
Status: New => Confirmed
** Changed in: webbrowser-app (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1561002
Title:
Add automated tests to prevent API breakage for Ubuntu.Web
Status in webbrowser-app package in Ubuntu:
Confirmed
Bug description:
The webbrowser-app source package is what provides the Ubuntu.Web QML
component. However, this component is not properly versioned in a
stable way that aligns with the UITK versioning. As a result, apps are
broken simply by newer versions of the package being included in
updates.
For example, if one has an application that uses Ubuntu.Web, but was
still using the older Ubuntu.Components import, the newer version of
Ubuntu.Web imports the newer Ubuntu.Components, which creates
conflicts, and results in various aspects of the app being broken, in
particular many elements have improper theme rendering.
As a supported part of the SDK, this should never happen, and QML
imports should be version stable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1561002/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
