Hey Shubhangini,
The answer to your question is a bit technical. Basically, every page that can appear in the iframe must give permission to the outer website that it may embed its content.
For example, the https://support-driven.tightknit.community site is currently configured to allow other sites to embed its content, including https://www.supportdriven.com.
However, https://live.remo.co is more restrictive and only allows a small number of sites to embed its content. https://www.supportdriven.com is not included in the list. That's why when you click the link to remo within the iframe, the browser prevents it from loading in order to respect remo's embed policy.
---
Now in terms of what we can do, I think the fix is actually pretty simple. 🎉 We don't have control over https://live.remo.co so it may not be realistic to ask them to change their embed policy. Instead, our team can change the event hyperlink to open in a new tab. So when you click the remo link, it will open an entirely new browser tab instead of loading within the iframe itself.
Does that experience sound reasonable to you?
