Profile for Arc Browser

[mamembrado]

Would be great to add support of chromium profiles for the Arc Browser (based on Chromium)

Don't hesitate to ping me for a referral link if needed :)

(and many thanks for Finicky, it's really a HUGE help in our day to day usage!!!)

[huyz]

To be clear, I think that in this case a Finicky profile should actually direct to an Arc space.

Luckily there's a workaround in the meantime: https://resources.arc.net/en/articles/7670020-air-traffic-control-route-links-to-the-right-space-automatically

[Luminus]

If you end up here you might find this pertinent CC: @huyz

Air Traffic Control in the Arc Browser is neat, but is also quite lacking in that it is absolute.

If you set Google Docs links to open in a specific Arc Space, this will apply to all of those links regardless of whether you've clicked the link in an external application (e.g. Slack) or in a different space within Arc.

I would've expected that links clicked in Space A open a tab in Space A. Instead, if you click a Google Docs link in Space A, it'll open up in Space B because of the way Air Traffic Control works.

[huyz]

Hmm I can see both behaviors being useful depending on the domain.

But this should be an Arc feature request as well

[unibeck]

Here is a solution I came up with to open a specific Arc Space depending on the app.

1. Add an arbitrary query string to the url, in my case finicky_dest_space=Work

        {
            match: ({ opener }) =>
                opener.path && opener.path.startsWith("/Applications/Slack.app"),
            browser: {
                name: "Arc",
            },
            url: ({ url }) => {
                return {
                    ...url,
                    search: url.search = url.search ? `${url.search}&finicky_dest_space=Work` : 'finicky_dest_space=Work'
                }
            }
        },

2. Then in Arc's Air Traffic Control setting, set up a route that looks for that aributary string and directs it to the correct Space

I have tested this with URLs with and without query strings, and it seems to be working fine so far!