Is there any other restriction/benefit in containers? I use the 'first party isolate' config option, and never really need e.g. different accounts logged in to same site, so as far as I'm aware there's no point?
I recently switched from an unmaintained tabs sidebar to 'Sidebery' which is quite nice in an 'overriding UI like it's made by Adobe' sort of way, which has got me using trees, and even tried containers (since unlike previous one it supports changing them and shows a coloured dot for which a tab is in) but I don't think it's gaining me anything.
With the first party isolate, mechanisms such as oAuth would not work. So the containers are less restrictive, but still allow you to have two sites with the same cookie context.
I've been using first party isolation for quite a while on desktop and Android and the only websites I experienced issues with are the Atlassian login and the Trello GitHub powerup.
Everything else, including tons of single sign in/OAuth websites, work without any issue.
Yep, ditto Atlassian. There's a big thread of people complaining about it on their forums too.
Unfortunately of course it'll always be a minority, and won't affect whether even those people (have to) use Jira or whatever, so not really any incentive for Atlassian to fix it.
I recently switched from an unmaintained tabs sidebar to 'Sidebery' which is quite nice in an 'overriding UI like it's made by Adobe' sort of way, which has got me using trees, and even tried containers (since unlike previous one it supports changing them and shows a coloured dot for which a tab is in) but I don't think it's gaining me anything.