63

Ota Thanks for thining it through. We need to simplify we do not have 100 developers like Chrome team.

It should probably be a part of global website settings.

I could imagine a setting here that says Open in Profile. There is no pattern matching, it works on subdomain basis.

      10 days later

      Vlad That makes sense. Would it be possible to have an option that allows selecting domain or subdomain matching?

      Please consider that in midterm an overview or list of configurations would be helpful. Maybe that is combinable with an overall overview for "website settings": Having a list of domains in a table view and the selected custom options.

          15 days later

          I'm currently juggling two GitHub accounts, one personal and one work. The way I have it set up is to use one in Safari and one in Chrome and then use a tool (Hammerspoon) as URL handler that opens URLs clicked in the right browser. This has two drawbacks:

          1. It only works when links are opened outside the browser, not from links clicked in the browser.
          2. I have to use two browsers, which is messy

          It would be awesome if the there was a way to configure URL/regex patterns that opens only certain URLs in the right profile in Orion. Something like github.com/work/* would open in the work profile and anything else in the default (personal) profile.

          • Vlad replied to this.
            10 days later

            eproxus Regex is probably too much to handle, our entire website settings uses the subdomain.

                2 months later
                2 months later

                I am also interested in having this feature implemented into Orion as a user of profiles for work and personal browsing. Subdomains would suffice in my use-case.

                  If you were to create a webapp for discord, you probably don't want external links to stay in the webapp,and you mgith want them to redirect to the main browser instance

                  Also, if you had a webapp for google docs, u might want all links in any webapp or browser to redirect to the google docs webapp.

                  this would make it more seamless to switch between webapps and the browser

                    I'm thinking of how the UI for this could work

                      8 days later

                      Interestingly the current behaviour is useful as it avoids difficult UX problems (should the link open in the main Orion instance or in a tab in the webapp?). Solutions like Unite resort to a very complicated system of rules to determine where the link should open.

                      For me it would be enough to open the link in a main Orion instance or, better yet, in the system default browser so it can trigger a browser picker like Choosy or Velja.

                        What Unite offers is very complicated, but very extensible and if done correctly, be very seamless and easy switching between the webapps
                        I'm wondering if something could be done to make it not as complicated, but just as good

                          For further reference, here's how Unite works. You can select to allow the webapp to browse any link or set up restrictions via whitelisting or blacklisting URLs. If you opt for whitelisting URLs, only those in the list will open links inside the web app, and URLs not matched will open in the default system browser. If you opt for blacklisting/disallowing URLs, the logic reverses.

                          I believe it to be somewhat confusing, and would prefer something like Choosy's UI so rules are more explicit. The "when this rule applies" list box would have "open inside webapp" or "open in default browser" or something like that as possible actions.

                          Anyway, this level of refinement seems non trivial and a considerable amount of work to me. Just launching the default browser app would allow me to use Choosy to build more complicated workflows.

                            We made a change in current RC, lets discuss if that works. We should keep it simple!

                            The webapps work very well but there's a behaviour with opening links that I think might be better changed. When you make a webapp of a chat app, I think generally a preferred behaviour is that any opened links not open inside the webapp but instead to open in the main Orion instance in a new tab. The same behaviour might be preferable with, say, a YouTube or Twitch webapp.

                            Video below showing behaviour with the Element webapp:

                              In my case, the links do open but my request will be a different behaviour, to open them in a new tab in the main Orion instance rather than inside the webapp.

                                Brief Summary
                                As a user, I'd like to be able to specify which URLs can be loaded in a web app window, so that other URLs that don't match my filter will automatically be opened up in a new Orion window.

                                Details:
                                Ideally, in the "Add This Site as a Web App" dialog, a text field will be included that allows users to write a comma-separated list of domain names as to what URLs are allowed to open in that window, like the following:

                                mysite.com,feedback.mysite.com,auth.mysite.com

                                This comma-separated list can contain also contain regular expressions or glob expressions (whichever the team prefers here):

                                *.mysite.com,[0-9]+.apples.mystore.com,

                                When a link is clicked, it will check the URL if it matches the filter. If it does, it will open in place as normal. Otherwise, it will open in a new window automatically.

                                Image/Video:
                                n/a

                                  Merged 2 posts from Add a URL filter to web apps.
                                    Merged 5 posts from Option to open links in webapps in main browser instance.