4 ms·

This needs to be bypassed to use SSO, to bypass it the SSO providers site will need to ask for Storage Access, in some cases the user will be asked for permissi

This needs to be bypassed to use SSO, to bypass it the SSO providers site will need to ask for Storage Access, in some cases the user will be asked for permission… “After the user has granted access, Firefox will remember the storage permission for 30 days.” So lay users will get used to just clicking through and blindly granting the permission. The end result will be an additional step for trackers, and a bunch of headaches for all the legit services that get broken from this change. I’m all for less tracking but this doesnt seem like a good solution.

swiley 6y ago
At least they're getting asked. That's a huge improvement over what was there before. I still prefer the lynx UI: prompt yes/no/always for accepting any cookie.
- ancarda 6y ago
  It's a shame that "always" will whitelist a whole site though. It'd be nice if Lynx whitelisted a cookie name (per site). That way I could permit "PHPSESSID", but not "_ga". I never found a Firefox plugin that let me whitelist specific cookies. I might try to write one when I have time.
  - nerdponx 6y ago
    +1 to both of these. That'd be a killer feature for me in both Lynx and Firefox.
marcosdumay 6y ago
> So lay users will get used to just clicking through and blindly granting the permission. Does it break anything else besides cookie based SSO? Because for those, people will probably just login into the site, and ignore the permission. Firefox is also adopting the policy of not showing those permission windows at most cases, just showing a small notification. It's not clear on that page if this is one of those cases. Anyway, I agree that limiting the permissions to 30 days is bad. The users should be entitled to make permanent changes, and revert them themselves when they want. Firefox should at least give them the option, even if it's not the default one.
- treis 6y ago
  Lots of third party stuff like chat widgets and shopping carts are going to break. Had to deal with this when Chrome did their 3rd party cookie stuff. It's not insurmountable but adds friction for stuff like that.

swiley 6y ago

At least they're getting asked. That's a huge improvement over what was there before. I still prefer the lynx UI: prompt yes/no/always for accepting any cookie.

ancarda 6y ago
It's a shame that "always" will whitelist a whole site though. It'd be nice if Lynx whitelisted a cookie name (per site). That way I could permit "PHPSESSID", but not "_ga". I never found a Firefox plugin that let me whitelist specific cookies. I might try to write one when I have time.
- nerdponx 6y ago
  +1 to both of these. That'd be a killer feature for me in both Lynx and Firefox.

marcosdumay 6y ago

> So lay users will get used to just clicking through and blindly granting the permission. Does it break anything else besides cookie based SSO? Because for those, people will probably just login into the site, and ignore the permission. Firefox is also adopting the policy of not showing those permission windows at most cases, just showing a small notification. It's not clear on that page if this is one of those cases. Anyway, I agree that limiting the permissions to 30 days is bad. The users should be entitled to make permanent changes, and revert them themselves when they want. Firefox should at least give them the option, even if it's not the default one.

treis 6y ago
Lots of third party stuff like chat widgets and shopping carts are going to break. Had to deal with this when Chrome did their 3rd party cookie stuff. It's not insurmountable but adds friction for stuff like that.