BUG REPORT:

With Tweetbot 3.3.3 and Choosy 2.1 under macOS 10.15.6, if I view a tweet from the @consequence account that contains a link and I try to click on that link, the Choosy browser chooser appears, but the link bar underneath is empty, and clicking on a browser doesn't work. (Nothing happens.)

So far I am only able to reproduce it with links from that particular Twitter account, which are shortened with a custom scheme using the form

http://cos.lv/xxxxx

Something in this doesn't agree with Choosy's default behaviour.

HOWEVER, if, instead of simply clicking on the link, I right-click on the link and select "Open in Choosy", then the browser chooser that appears does work as expected.

I am able to either use the Open in Choosy workaround or to create a custom rule for Tweetbot that doesn't open the chooser at all and automatically goes to my default browser (which works for me most of the time), but it's not ideal.

Intriguingly, if I try to add another condition to the rule to limit it to web addresses in Tweetbot containing "cos" or ".lv", it doesn't work. So the rule can only work for ALL links in Tweetbot, not just links from that particular Twitter account.

This started for me after I upgraded to Catalina (even before 10.15.6). So I suspect that users with previous versions of macOS won't be able to reproduce. But presumably Catalina users will.

I am trying to identify other Twitter accounts whose links suffer the same fate when trying to use Choosy in Tweetbot. I'll post a comment if I find some.

I would really appreciate the option for in-browser links to be routed through Choosy. I use many Site-Specific Browsers and I mainly bought Choosy to have it automatically direct to the appropriate SSB while using my main browser.

For example. I'd like to direct all YouTube URLs to an SSB of a specific account. If I I'm not paying attention, which is likely to happen eventually, I'll slip up and forget to open the url with Choosy.

I read an older comment that it was by design, but I think it's worth reconsidering. Choosy could default to the way it works now, but adding the option to enable in-browser routing would expand the use cases for Choosy.

Thanks for the consideration, and thanks for Choosy!

I love the idea of Choosy - but I can't quite get it to fully work :(

What I'd like to happen is when I click on a link in Safari, the link gets opened directly in Firefox instead of as a new tab in Safari. The documentation suggests this is easy to accomplish, but no combination of settings that I've tried have worked (for any combination of browsers and rules). I've enabled the "Enable Choosy for links" option, and tried various flavors of rules, but nothing behaves differently.

It's worth noting that other core features of Choosy are working for me:
- Choosy shows up in the context menu (when I right click on links in the browser)
- The Safari and Firefox browser extensions seem to work properly

Here are the version of software I'm using:

Choosy 2.1
MacOS 10.14.6
Safari 13.1.1
Firefox 68.6.1esr
Chrome 83.0

Also note that I'm using my work computer, so maybe there are certain permissions which Choosy needs which have been disabled?

Any advice is appreciated!

Sometimes I'd like to open a link in a new browser window. If I'm inside a browser I can hold down (generally) shift when I click the link, and a new window will be opened. However, Choosy doesn't seem to expose a way to do this.

I think this can be implemented without interfering with the existing modifiers feature, by having the behavior change occur once the popup is already open. Because not all browsers would support this, it could probably be signposted by changing the label on supported-browsers to e.g. "Firefox (new window)" once the modifier is pressed.

Firefox and Chrome both require a command line parameter to trigger this behavior: --new-window

I'm not certain how to do this with Safari.