Embedded IFRAME Google Calendar not working in version Greater Then 100
I am Using Iframe embed in Google calender.But its not working now from latest version of firefox.Upto version 100 no issue. My site is in Google App Engine.
Like this Showing
Firefox Can’t Open This Page
To protect your security, accounts.google.com will not allow Firefox to display the page if another site has embedded it. To see this page, you need to open it in a new window.
can you please Suggest me the solution
Ausgewählte Lösung
What CSP (content-security-policy) messages do you see in the Web Console ?
This might only be about third party cookie partitioning (cookie isolation) that prevents the Google Calendar page from getting the Google session ID cookies casing you to get the Google account login page. You can try to set network.cookie.cookieBehavior = 4 to disable partitioning if this pref is currently set to 5 to see if that has effect.
You may have to clear existing cookies for the Google account.
You can open the about:config page via the location/address bar. If you get the warning page, you can click the "Accept the Risk and Continue" button.
Diese Antwort im Kontext lesen 👍 0Alle Antworten (4)
safiyullah.mohideen said
To protect your security, accounts.google.com will not allow Firefox to display the page if another site has embedded it. To see this page, you need to open it in a new window.
Steps to replicate the issue and screenshots please. The above message is from Google. This is interesting, would love to see if we can replicate. Let get Win11 ready.
Geändert am von jonzn4SUSE
Ausgewählte Lösung
What CSP (content-security-policy) messages do you see in the Web Console ?
This might only be about third party cookie partitioning (cookie isolation) that prevents the Google Calendar page from getting the Google session ID cookies casing you to get the Google account login page. You can try to set network.cookie.cookieBehavior = 4 to disable partitioning if this pref is currently set to 5 to see if that has effect.
You may have to clear existing cookies for the Google account.
You can open the about:config page via the location/address bar. If you get the warning page, you can click the "Accept the Risk and Continue" button.
Geändert am von cor-el
This might only be about third party cookie partitioning (cookie isolation) that prevents the Google Calendar page from getting the Google session ID cookies casing you to get the Google account login page. You can try to set network.cookie.cookieBehavior = 4 to disable partitioning if this pref is currently set to 5 to see if that has effect.
Above solution is perfectly worked for us.I have another question.
If we set network.cookie.cookieBehavior = 4 from 5 means , is this safe?
Having set this pref to 5 means that you isolate (partition) cross-site cookies like explained in the total-cookie-protection article. This setting can break website that use cross-site cookies.
Selecting "Cross-site tracking cookies, and isolate other cross-site cookies" sets this pref to '5' and enables Total Cookie Protection. Selecting "Cross-site tracking cookies" sets this pref to '4' and does not partition/isolate cross-site cookies.
- https://support.mozilla.org/en-US/kb/introducing-total-cookie-protection-standard-mode
- https://blog.mozilla.org/en/products/firefox/firefox-rolls-out-total-cookie-protection-by-default-to-all-users-worldwide/
Total Cookie Protection creates a separate cookie jar for each website you visit. This means that a third-party (ad) website can't track you across other websites you visit where it is embedded. In this case this means that if you logged in to Google by visiting a Google website that you aren't logged in if you access a Google website embedded on another page and this will fail since you can't login via this iframe as this is prohibited via CSP. There are two options, one is to disable Enhanced Tracking Protection for this website via the shield icon and the other option is to disable Total Cookie Protection.
