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

Friction adding a site to a container: requires visiting it after unchecking "Limit To Designated Sites" #1828

Closed
jimaldon opened this issue Jul 21, 2020 · 7 comments

Comments

@jimaldon
Copy link

There's a lot of friction when it comes to adding a site to a container. Since there's no option to manually input URLs to the designated sites list, I need to visit a website in the container I need in order to add it to the list. But I'll constantly be kicked out of the container if I have "limit to designated sites" enabled.

The situation is worse if the site in question is a subdomain which the server is configured to automatically redirect users from. In this case, you can't add it to the list since you can't manually visit it.

@redbaron-gt
Copy link

Needs manual input of URL for containers functionality. For example I cant add AWS console user URL like https://1234234234.signin.aws.amazon.com/console because it always redirects to different page when entered.

@jimaldon jimaldon changed the title Lot of friction adding a site to container: requires visiting it after unchecking "Limit To Designated Sites" Friction adding a site to a container: requires visiting it after unchecking "Limit To Designated Sites" Jul 22, 2020
@adamalton
Copy link

This is very much related to #1830 and #1670

@sdht0
Copy link

sdht0 commented Aug 5, 2020

I face this issue as well, when websites redirect to other domains for login/payments and it is very hard to add all the domains to the container.

One idea comes to my mind and should be simple enough to implement. If "limit to designated sites" is enabled and the user/a redirect tries to open a website that is not in the assigned list, the user should get a prompt to either "confirm opening in default container" or "assign domain to this container and continue". This will be especially useful for redirects across multiple "short-lived" domains (some sites do this), which would be difficult to find out and add manually even if #1830 were to be implemented.

A 3rd option could be to "temporarily allow opening in this container" or even "temporarily disable limit to designated websites", e.g., for payments sites, that could be common to multiple other sites, similar to #1834.

@adamalton
Copy link

I like the suggested solutions above from @sdht0, particularly the first one.

@blis5fool
Copy link

I'm currently facing this issue for something as simple as clicking print button after opening a PDF from Gmail because it performs several redirects as @sdht0 mentions above.

I also like first suggestion by @sdht0 and I think it would also be helpful to be able to enter URL manually but with wildcard like "*.google.com"

@grahamperrin
Copy link

friction

▶ 2017 issue #719 with multiple duplicates

manually input URLs

▶ 2017 issue #839 with multiple duplicates

@jimaldon please consider closing this issue so that other issues may be more easily managed. Thank you.

@grahamperrin
Copy link

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants