Currently, if a user sets a specific browser for a shortcut but later uninstalls that browser, the command fails to execute without any notification or error message.
Suggested Approaches:
-
Show a Toast or Popup: Inform the user that the executable was not found.
-
Fallback to Default: Automatically open with the default browser.
-
Popup with Redirect: Show a popup and guide the user to the Edit page.
I suggest going with Option 1. We should avoid silently "helping" the user by switching browsers without notice.
Regarding Option 3: Based on my current understanding of CmdPal, this might not be feasible at the moment because certain functionalities, such as GoToPage, appear to be unfinished or not yet available. However, it might be possible to implement a redirect or guidance without relying on GoToPage. I'm not entirely sure yet and it would require further research.
@Daydreamer-riri
Currently, if a user sets a specific browser for a shortcut but later uninstalls that browser, the command fails to execute without any notification or error message.
Suggested Approaches:
Show a Toast or Popup: Inform the user that the executable was not found.
Fallback to Default: Automatically open with the default browser.
Popup with Redirect: Show a popup and guide the user to the Edit page.
I suggest going with Option 1. We should avoid silently "helping" the user by switching browsers without notice.
Regarding Option 3: Based on my current understanding of CmdPal, this might not be feasible at the moment because certain functionalities, such as
GoToPage, appear to be unfinished or not yet available. However, it might be possible to implement a redirect or guidance without relying onGoToPage. I'm not entirely sure yet and it would require further research.@Daydreamer-riri