oxide requires app to provide standard browser dialogs

[dobey]

Currently, in order for applications to work properly with sites that use JavaScript dialogs, Oxide requires each application to provide these same standard UI components, and has no default behavior when they are not provided. This requires applications which need to embed Oxide for some reason, to provide additional code. There's no particularly good reason for the Oxide component to require this, rather than providing its own standard versions.

Please merge these dialogs from webbrowser-app into Oxide and use them as standard items, rather than requiring every app to provide the same things.

(This should also be done for the basic auth, and proxy auth support as well, as reported in bug #1422534 and bug #1422339.)

[Olivier Tilloy (osomon)]

It would make sense to provide default dialog implementations indeed, but this shouldn’t pull in a dependency on Ubuntu.Components.

[Chris Coulson (chrisccoulson)]

So, this is basically carry over from QtWebkit. It makes sense and I would like to eventually have default implementations of the UI components provided by UbuntuWebView in Oxide (having an auxiliary UI provider for Ubuntu.Components with the possibility of adding one for QtQuick.controls too. Having a soft-dependency on either of those isn't a problem).

If we do this, it would make sense to provide additional mechanisms for applications to intercept things like JS alerts and HTTP auth requests so it can handle them without displaying the default UI

[dobey (dobey)]

@Chris, I'd be fine with keeping the API to allow apps to do that if they really want to. The main problem I have is that it's currently a requirement for apps to do this.

[Chris Coulson (chrisccoulson)]

This is actually in progress, although the work is being tracked in https://blueprints.launchpad.net/oxide/+spec/ubuntu-webview-implementation instead.