3 ms·
Regards the containers, I started my profile compartmentalization practice before they arrived, so I never explored them. But I'm curious as to whether each con
by ttctciyf 4y ago
Regards the containers, I started my profile compartmentalization practice before they arrived, so I never explored them. But I'm curious as to whether each container comes with a complete set of browser permissions, like profiles do, which would enable you (for example) to have a location-enabled container specifically for google maps (in reference to[0]) while disabling it on the container used for search, as you could quite easily do with profile compartmentalization? (Which, tbf, is a privacy rather than a security concern.)
0: https://www.simpleanalytics.com/en/blog/google-changed-google-maps-url-your-location-data-is-no-longer-safe https://www.simpleanalytics.com/en/blog/google-changed-googl...
- paulryanrogers 4y agoAdd-ons cross over container boundaries, so I suspect other browser permissions do too. You're solution is more bullet proof. For similar reasons I am hoping to add better profile support to Browser Routr.