The current implementation of the onDownloadRequested signal handler in the browser, on desktop, does this:
Qt.openUrlExternally(request.url)
(as opposed to the touch version which uses the DownloadManager API to actually download the requested URI).
This means that the requested URI will be opened and downloaded in the default browser. If the default browser has been set to webbrowser-app, this will open another webbrowser-app instance (multiple windows are not well supported by the way) pointing to the requested URI, which will, obviously, not be downloaded. In both cases, a rather bad UX.
The current implementation of the onDownloadRequested signal handler in the browser, on desktop, does this:
Qt. openUrlExternal ly(request. url)
(as opposed to the touch version which uses the DownloadManager API to actually download the requested URI).
This means that the requested URI will be opened and downloaded in the default browser. If the default browser has been set to webbrowser-app, this will open another webbrowser-app instance (multiple windows are not well supported by the way) pointing to the requested URI, which will, obviously, not be downloaded. In both cases, a rather bad UX.