Open Prometheos2 opened 5 years ago
Prometheos2
commented
5 years ago Well, I've tried without this add-on and with Firefox Multi-Account Containers and, it seems like it doesn't really work, even if both the Facebook account is connected and the page is into the container.
It might rather be an issue that takes root in their add-on, then.
Needs additional testing, though.
maxxcrawford
commented
5 years ago We have an internal discussion going how to "toggle" this add-on on a per-site basis. We'll open an issue to keep this on track. Thanks!
NewAlexandria
commented
5 years ago This issue has come up with other container-izers, too, and some of the forks have tried to implement it, or want to.
It would be great to see support for this in the core.
Though you may not want to support a default list (since this just nerfs the container-izer), you may want to support a list of suggested exceptions, so that when someone visits a site and has an SSO-login problem, the suggestion could be easier made.
Siedlerchr
commented
5 years ago Another idea would be to have it like ublock origin etc. temporarily disable it for a site.
Mello-Yello
commented
5 years ago I don't know if this is the right location to comment, but inside the add-on, on a site that has been sandboxed, by clicking on "Sites Allowed in Facebook Container" there's a list of "SITES YOU HAVE ALLOWED", which hints to the ability to whitelist some specific websites. Is that just a stub for a future feature?
JJRicks
commented
4 years ago Bump?
luckied
commented
4 years ago Why can't we disable functionality for a site, as already mentioned?! Seems crazy to have a section for sites we've allowed, but are unable to do so...
maxxcrawford
commented
4 years ago Quick update for everyone tracking this issue – we have a feature that has been created and is being reviewed now that allows you to add/remove any site to the Facebook Container using the extension panel/doorhanger. Follow it's progress on this issue #422
Because this issue is about temporarily adding site to the FB Container, this issue is still relevant.
Perceived problem: It is a very helpful add-on, but it blocks the websites' integrated comments widget, which, while planned for, I find a bit annoying.
Possible solution: Allowing the user to temporally put websites into the Facebook container for that may solve the issue.
I don't forcibly mean a whitelist or something, but simply being able to re-open a tab into the Facebook container.
I assume this might create an issue if other tabs/links are opened from Facebook, which might then be in the container due to the removal of the "filter" on the container; so I would understand if it doesn't get accepted.