focused view fails in safari

  • 15 April 2024
  • 5 replies


I have implemented focused view in my application and it works when i use chrome,
but when i use safari it fails and I get’s stuck in an endless loop of loading.

this is the message i’m getting: 
Refused to load*********insession=1&ti=3c31d6822d2******fc4 because it does not appear in the frame-ancestors directive of the Content Security Policy.

important to note that: 
the frame-ancestors directive also includes the domain from which i’m running the code.

in addition i get this errors too:
Error while parsing the 'sandbox' attribute: 'allow-downloads' is an invalid sandbox flag.
[Error] Failed to load resource: the server responded with a status of 403 () (, line 0)
and a few more...

will appreciate any data about why it happened and how to solve it. 

5 replies


Hey @doronW

We could see that you raised a support issue with us and we’ll cover your case from there. 

In theory, nothing changes when using a different browser to load focused view, so considering that we need to investigate your case a bit more in-depth with our support teams to understand what is happening. 

Thank you for your message!



Was any solution found for this? We have the exact same issue.


Hi @ovidiu.anghelina,

Can you confirm which values you are providing to frameAncestors array in your embedded signing generation?

Probably the value you are sending for this array (and messageOrigins as well) are impacting the content to be loaded.



For the frameAncestors we provide 2 URLs - the URL of the FE where the focused view is displayed and as we’re using the demo environment

For the messageOrigins we only provide

From what we can tell this is aligned with the documentation that you have also linked, and without those values it wouldn’t have worked on Chrome or Firefox either.





Yeah, these values (your front-end domain and [demo] or [prod]) are the correct ones. Safari should load properly your focused view component. Recent cases from Safari users were because it was set a different frameAncestors value where it was possible to be loaded from all browsers but Safari wasn’t able to do it. 


It would require a further investigation with code snippets and HAR files to understand what is going on. 


Could you please raise a ticket request to our support team so we can review this accordingly?


Thanks in advance!