After a bit of further work it looks like the "downloadRequested" signal probably isn't necessary (at least from the perspective of the webbrowser-app), as this can be handled purely within QML from the context actions. So only "unssportedContent" is needed for file types that the browser can't display natively.
After a bit of further work it looks like the "downloadRequested" signal probably isn't necessary (at least from the perspective of the webbrowser-app), as this can be handled purely within QML from the context actions. So only "unssportedContent" is needed for file types that the browser can't display natively.