I've recently updated from a much earlier version and ran into the following, somewhat comical issue.
So lets say the following is true:
BrowserPicker is set as the default browser
You don't have some of the needed runtimes for it
When you open a link you get a window warning you about the lacking runtime and a link to it. But, what happens if you click that link? Another BrowserPicker opens with the same warning. Nor can you copy that link from the window. So you end having to manually type in the link.
I'm not the first person who ran into this, so it's at least worth to discuss as an issue.
Though I'm not entirely sure what should be done here, because BrowserPicker is not working yet at that stage and that window is probably not modifiable to allow the copy from it. One option I could think of is removing BrowserPicker from being the default browser on installation, ideally only if the user is lacking the necessary runtimes.
I've recently updated from a much earlier version and ran into the following, somewhat comical issue.
So lets say the following is true:
When you open a link you get a window warning you about the lacking runtime and a link to it. But, what happens if you click that link? Another BrowserPicker opens with the same warning. Nor can you copy that link from the window. So you end having to manually type in the link.
I'm not the first person who ran into this, so it's at least worth to discuss as an issue.
Though I'm not entirely sure what should be done here, because BrowserPicker is not working yet at that stage and that window is probably not modifiable to allow the copy from it. One option I could think of is removing BrowserPicker from being the default browser on installation, ideally only if the user is lacking the necessary runtimes.