Is there any way to allow sandbox properties for the new beta Custom Components? I am missing properties such as "allow-top-navigation" etc which exist on the legacy custom components.
2 Likes
Hey @Klas_Jersevi! Welcome to the community. 
That's actually a great question that I hadn't considered before. Out of the box, it looks like the custom component iframe comes with the following:
Like you said, it's missing allow-top-navigation and a few others that were options in the previous iteration of the custom component. I haven't seen any specific mention of this internally or in our public documentation, but will reach out to the team to see if its on the roadmap. 
I'll update you here when I hear back!
Hey Klas,
could you share a little bit more about your use case regarding allow-top-navigation? Could allow-top-navigation-by-user-activation work for your case?
So, our use case is that we want to open ms-word: links (Office URI:s) that opens documents in office using webdav. Our lib opens them in top window for cross-browser/platform compatibility reasons. These are usually opened on clicks, so my guess is that allow-top-navigation-by-user-activation should be fine.