Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: ability to set certain browsers to only appear with certain rules (URIs/protocols/domains), like Android #111

Open
sjain882 opened this issue Mar 28, 2024 · 0 comments
Labels
Feature Enhancement Update existing feature
Milestone

Comments

@sjain882
Copy link

According to this proposal, if I open any normal link, I would see the following example browsers:

Chrome, Edge, Firefox

If I open a rule-matching link (like https://steamcommunity.com/sharedfiles/filedetails/?id=1644959932), I would see the following browsers:

Chrome, Edge, Firefox, Steam

This way, I can choose whether I want to open this Steam link in my browser (e.g, if I want to use a Chrome extension's feature for the Steam website), or if I want to open it in my Steam client (e.g, to subscribe to the item since I am already logged in there)

This is not the only use case for this type of feature. For example, I can choose whether to open a Discord link in my client (main account), or the Edge browser (university account).

This means that I don't have to see a browser/icon I rarely use (clutter) every time I use Hurl.

However, It also means that I when I do need that browser/icon, I have the option easily available, rather than having to painstakingly type it into the Run box.

This is how Android does things (app URL associations), and it's perfect UX in my opinion.

(To note, I did try using the recently released rulesets feature to replicate this behaviour, and tested the match, but nothing seems to actually happen when I click a rule-matching link, so I'm not sure what the feature does exactly / it's not working for me)

@U-C-S U-C-S added the Feature Enhancement Update existing feature label Apr 1, 2024
@U-C-S U-C-S added this to the v0.11 milestone Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Enhancement Update existing feature
Projects
None yet
Development

No branches or pull requests

2 participants