is your parent window http or https?

FreeLink/甫连信息
🌍 DocuSign Partner | Partner Profile
🌟 The only DocuSign Partner globally certified as both a Certified eSignature Administrator and eSignature Technical Consultant
🏆 DocuSign 2024 APAC Reseller Growth Partner of the Year
💡 Ranked #1 in the OG All Star category in DocuSign Community Wrapped 2024
📊 DocuSign Community Leaderboard Top 5 contributor
🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries
🔗 Connect with me on LinkedIn: https://www.linkedin.com/in/gehengfeng/

Hi Hengfeng Ge,

It is https.

Could you check is there any error message in the console and provide the screenshot network for Chrome develope tool.

FreeLink/甫连信息
🌍 DocuSign Partner | Partner Profile
🌟 The only DocuSign Partner globally certified as both a Certified eSignature Administrator and eSignature Technical Consultant
🏆 DocuSign 2024 APAC Reseller Growth Partner of the Year
💡 Ranked #1 in the OG All Star category in DocuSign Community Wrapped 2024
📊 DocuSign Community Leaderboard Top 5 contributor
🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries
🔗 Connect with me on LinkedIn: https://www.linkedin.com/in/gehengfeng/

I'm currently unable to reproduce the issue, but I recall it was related to a frame-ancestor: self error.

Reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/frame-ancestor

That error used to appear every time I refreshed the page, even though the page rendered correctly—so I'm not entirely sure if it's directly related to this issue.

Are you embedded signing for focused view? Have you read this document?

https://www.docusign.com/blog/developers/15-minutes-to-better-ux-enhancing-embedded-signing-focused-view#augmenting-the-experience:-docusign-js-and-focused-view

and the these two parameter should setup.

    "frameAncestors": ["https://my.site.com", "https://apps-d.docusign.com"],
    "messageOrigins": ["https://apps-d.docusign.com"]

could you check it?

FreeLink/甫连信息
🌍 DocuSign Partner | Partner Profile
🌟 The only DocuSign Partner globally certified as both a Certified eSignature Administrator and eSignature Technical Consultant
🏆 DocuSign 2024 APAC Reseller Growth Partner of the Year
💡 Ranked #1 in the OG All Star category in DocuSign Community Wrapped 2024
📊 DocuSign Community Leaderboard Top 5 contributor
🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries
🔗 Connect with me on LinkedIn: https://www.linkedin.com/in/gehengfeng/

We are currently using the default display. Instead of using an iframe, we are going to open the DocuSign URL in a new tab to avoid potential issues in the future as mentioned in article.

‘https://www.docusign.com/blog/developers/new-browser-security-settings-and-iframes’(‘Usually a better solution is either to redirect the browser to the signing ceremony’s URL, or to open a new tab in the browser for the signing ceremony’ ).

Thanks for your help.

Yes, that’s good idea,  loading a Docusign page in a new tab can really reduce a lot of problems.

FreeLink/甫连信息
🌍 DocuSign Partner | Partner Profile
🌟 The only DocuSign Partner globally certified as both a Certified eSignature Administrator and eSignature Technical Consultant
🏆 DocuSign 2024 APAC Reseller Growth Partner of the Year
💡 Ranked #1 in the OG All Star category in DocuSign Community Wrapped 2024
📊 DocuSign Community Leaderboard Top 5 contributor
🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries
🔗 Connect with me on LinkedIn: https://www.linkedin.com/in/gehengfeng/