I can reliably reproduce with the steps in the description. I guess
google generates intent:// URLs because it thinks it’s talking to an
android device, which is very unfortunate. Not sure what’s the best way
to address that. Maybe a UA override for google.com, or a custom
protocol handler to intercept intent:// URLs (or even intercepting them
at the navigationRequested level).
** Changed in: webbrowser-app (Ubuntu)
Status: New => Confirmed
** Also affects: webbrowser-app
Importance: Undecided
Status: New
** Changed in: webbrowser-app
Status: New => Confirmed
** Changed in: webbrowser-app
Importance: Undecided => 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/1384361
Title:
Clicking on google "intent" url leads to error pages
Status in Oxide Webview:
New
Status in Web Browser App:
Confirmed
Status in “webbrowser-app” package in Ubuntu:
Confirmed
Bug description:
Using rtm 122
- open the webbrowser
- go to google.com
- search for e.g "Washington"
- click on the map image at the top of the results
-> you get an error about "intent:/..." not being supported
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1384361/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
