In oxide, the CHROME_VERSION_STRING token contains the chromium version
that it’s built against, so we could possibly expose that to the QML API
as a readonly property of OxideQQuickGlobal.
** Also affects: oxide
Importance: Undecided
Status: New
--
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/1565063
Title:
Update the chromium version in the user agent
Status in Oxide:
New
Status in webbrowser-app package in Ubuntu:
Confirmed
Bug description:
We have never updated the version, which is 35, and now we are based on 49
While this may not have any impact it does reflect the core support we have,
and its possible some sites may check it.
Ideally we would query oxide for this dynamically.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1565063/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
