Cross origin frame error after updating to Edge 98+

[Yaseenkk]

Started cross origin frame error after updating to Microsoft Edge 98+. It was working fine with an older version of Edge and also works in all versions of Google Chrome.

Also tried to set same value to document.domain in both parent document and in iframe loaded document.

Any recent change or updating causing this error in edge?. No preflight requests logs in network tab. Does anyone know is it a known issue in edge version 98+ and appreciate if you could share any workaround to resolve?

[#2]

@Yaseenkk Hello!  We normally publish any site compatibility-impacting changes here: https://docs.microsoft.com/en-us/microsoft-edge/web-platform/site-impacting-changes

Specifically for v98 this is listed in the documentation: 

Have you tried to test on the current version of MS Edge v101?  Does it reproduce there as well?  Thanks!

-Kelly

[#3]

Hi @Kelly_Y,
Thanks for your reply. Tried in latest version of MS Edge V101 - still same issue.

Regards,

Yaseen

[#4]

@Yaseenkk Do you have a repro we could look at? Or at least un-censored error messages? What are the two origins (top-level page, and frame)? Did you verify the expected content had loaded into the frame (and was not blocked by Tracking Prevention)?

Generally speaking, nothing should have changed here recently; there is a plan to remove the ability to use document.domain to relax Same-Origin-Policy, but that change won't land until Edge 106: https://docs.microsoft.com/en-us/deployedge/edge-learnmore-origin-keyed-agent-cluster