Comment 2 for bug 1679599

I don't think this is desired. UbuntuWebView deprecates the legacy API points for providing UI components and making them unavailable in the new webview is deliberate.

The context menu is already customizable via an API that allows the application to add / remove actions. The internal context menu implementation depends on functionality that we're probably never going to expose in a public API (specifying the referrer URL in page loads), so it's not actually possible right now to provide a fully featured context menu by replacing the UI component wholesale anyway (and that's going to be even more true when features like spell check get added).

There's a separate bug already for allowing applications to handle JS dialogs (bug 1637197), but that's not going to use the legacy API. It will be a new API using a signal, which is a lot more flexible and will allow the application to do things like implement its own queuing mechanism.

I'm not sure what to do about the content picker issue yet.