IFrame Cookies in Firefox 101
My site that uses Twitch.tv iframes no longer works because the Twitch iframes are unable to access their own cookies. When attempting to take any actions in the iframes, they ask to log in, and when the login flow is completed, nothing changes, it continues to not have the login state transfer over to the iframe. I'm hoping this is unintentional as it breaks entire use cases of iframes. I have no need to access the cookies myself, just let the site that is being frames access its own cookies!! This is WITHOUT the new protections that are in testing right now, but those ALSO were breaking it. Now it is broken even with them turned off. I will be using Edge for the foreseeable future until this is fixed I suppose... Love Mozilla and privacy but this is broken, sorry.
被選擇的解決方法
So, I booted up FF today to check on this, and now it is working? I'm on the same version (101.0.1) as I was before but the issue is gone now. Nothing changed that I'm aware of so I now suspect this was an issue on Twitch's end and they've resolved it but I'm still not sure what the actual root cause was. Thanks for the quick responses though! Super happy to be back on FF.
從原來的回覆中察看解決方案 👍 0所有回覆 (3)
"First Party Isolation" or "Total Cookie Protection" sets separate third party cookies based on the site hosting the frame. So it's natural that a twitch frame on site1 doesn't see a login in a twitch frame on site2. However, it shouldn't be a problem if your site hosting the various frames is using the same host name for all of the pages. That sounds like a bug.
Anyway, if you disabled this feature, I think you need to log in again to have Firefox set cross-site third party cookies again like the old days. I'm not sure how to test all this...
See:
選擇的解決方法
So, I booted up FF today to check on this, and now it is working? I'm on the same version (101.0.1) as I was before but the issue is gone now. Nothing changed that I'm aware of so I now suspect this was an issue on Twitch's end and they've resolved it but I'm still not sure what the actual root cause was. Thanks for the quick responses though! Super happy to be back on FF.