You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
I pushed a button by mistake. I didn't 'update to the latest version of 'Multi-"Account Container' because I don't know how and don't know what it is.
Actual behavior
Every time I want to open Google mail, I get this message: 'Open this site in your assigned Container'. Then I have to push a button 'Open in Container'. By mistake I must have asked Firefox to always open Facebook for this site. This is a big hassle. I want this to go away. I am not tech savvy.
Expected behavior
I just want to click on google mail and have it open without this annoying message. It's an unnecessary step every time I try to open my Gmail which is all of the time.
Additional informations
No response
Provide a copy of Troubleshooting Information page (optional)
No response
The text was updated successfully, but these errors were encountered:
Before submitting a bug report
Step to reproduce
I pushed a button by mistake. I didn't 'update to the latest version of 'Multi-"Account Container' because I don't know how and don't know what it is.
Actual behavior
Every time I want to open Google mail, I get this message: 'Open this site in your assigned Container'. Then I have to push a button 'Open in Container'. By mistake I must have asked Firefox to always open Facebook for this site. This is a big hassle. I want this to go away. I am not tech savvy.
Expected behavior
I just want to click on google mail and have it open without this annoying message. It's an unnecessary step every time I try to open my Gmail which is all of the time.
Additional informations
No response
Provide a copy of Troubleshooting Information page (optional)
No response
The text was updated successfully, but these errors were encountered: