touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #42304
[Bug 1399601] Re: Ubuntu.Web’s WebView.getUAString() is racy by design
** Branch linked: lp:ubuntu/vivid-proposed/webbrowser-app
--
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/1399601
Title:
Ubuntu.Web’s WebView.getUAString() is racy by design
Status in the base for Ubuntu mobile products:
Confirmed
Status in Web Browser App:
In Progress
Status in webbrowser-app package in Ubuntu:
In Progress
Status in webbrowser-app package in Ubuntu RTM:
Confirmed
Bug description:
See http://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Web.WebView
/#getUAString-method for documentation.
This method is being called by the WebView in Component.onCompleted,
and sets the shared context’s default user agent. If the WebView is
instantiated with a url set, the first HTTP request is issued before
getUAString() is called, and thus potentially with the wrong UA
string.
This API is racy by design, there’s really no way to fix it.
There are currently 2 apps in the store using this API:
com.viclog.2048
com.viclog.flappybird
and 3 more using it with the UbuntuWebView, which is version 0.1 of
the API, based on QtWebKit:
com.ubuntu.developer.andrewsomething.stackbrowser
com.ubuntu.developer.daker.x-type
com.ubuntu.developer.fcole90.feedspot
Seeing those relatively small numbers, I think it’s a good opportunity
to remove the API altogether, after ensuring that the apps are fixed
to not use it. Documentation will need to be updated.
UPDATE: as of 2014-12-11, com.viclog.2048 and com.viclog.flappybird have been updated in the store, they no longer use WebView.getUAString(). So effectively no application uses the API, and it should be safe to remove it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1399601/+subscriptions