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

No "forget" option for "always open in container" #2615

Open
2 tasks done
MarcusWolschon opened this issue Feb 13, 2024 · 4 comments
Open
2 tasks done

No "forget" option for "always open in container" #2615

MarcusWolschon opened this issue Feb 13, 2024 · 4 comments
Labels
bug Something is broken!

Comments

@MarcusWolschon
Copy link

Before submitting a bug report

  • I updated to the latest version of Multi-Account Container and tested if I can reproduce the issue
  • I searched for existing reports to see if it hasn't already been reported

Step to reproduce

  1. open a site in a container, checking the [X] alway in this container´´
  2. change your mind a few weeks later

Actual behavior

You can only assign another container to always open the site in but not to NOT change the current container

Expected behavior

An additional option in the container selction to forget about the container-assignment

Additional informations

No response

Provide a copy of Troubleshooting Information page (optional)

No response

@MarcusWolschon MarcusWolschon added the bug Something is broken! label Feb 13, 2024
@achernyakevich-sc
Copy link

@MarcusWolschon

Please, check check project's Wiki - see Frequently asked questions -> Remove "Always open in..." site from a container.

If it helps - close this issue.

@jd1
Copy link

jd1 commented Feb 15, 2024

I ran into the same issue and it worked exactly as mentioned in the FAQ.

It works, but is is not very intuitive. I would have expected to reset this on the same dialog where I also set "always open in container".

Edit: I just figured out that I can set and reset it via the right-click menu.

@achernyakevich-sc
Copy link

@jd1 and @MarcusWolschon This issue is reported as a bug but it is not a bug. So it need to be closed.

If you would like to change and make this functionality more user-friendly then I would recommend you to find corresponding issue(s), join discussion and leave comments/proposals there. For example, you could vote for the approach I proposed - #2294. :)

@MarcusWolschon
Copy link
Author

Thanks.
It's VERY well hidden.
So I guess we change this into a FEATURE REQUEST to give it a more obvious place.
My suggestion:
Additionally to the existing place, allow to reach this functionality in the page asking if the current tab should be opened in the designated container.

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

No branches or pull requests

3 participants