There is no doubt that we offer choice to users ;)
Webbrowser-app is not the default browser on the desktop and our webapp integration is now based on it. So we may still just have bridges between the 2 that don't take the browser setting into account.
Back to your problem, can you detail the use case where the browser alternative is not taken into account ? I can't reproduce the problem right now, as external webapp links are correctly opened with the default browser as far as i can see.
Can you may be detail the webbrowser-app or webapp package version?
There is no doubt that we offer choice to users ;)
Webbrowser-app is not the default browser on the desktop and our webapp integration is now based on it. So we may still just have bridges between the 2 that don't take the browser setting into account.
Back to your problem, can you detail the use case where the browser alternative is not taken into account ? I can't reproduce the problem right now, as external webapp links are correctly opened with the default browser as far as i can see.
Can you may be detail the webbrowser-app or webapp package version?