-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Playground embeds WordPress site within iframe without including the allow-top-navigation HTML attribute #1383
Comments
@miriamelementor in case we can't resolve this before WCEU, we could disable the onboarding flow and open a different page. |
@miriamelementor there's multiple places in WordPress where a link or a form uses |
Great catch @adamziel I missed this. |
@adamziel @bgrgicak Our team has resolved this issue, and can release it to Elementor's beta version (v3.22.0 beta 5) on June 3. Can Playground pull from a beta version? If not, GA is scheduled for June 9 which may be ok, it's just really close to WCEU so if there are issues we may not have time to resolve them. |
Elementor's "puzzle piece" is looking good, but there's a technical issue towards the end of the user onboarding process. It appears to be related to the playground embedding the WordPress site within an iframe without including the allow-top-navigation HTML attribute. This attribute, when set to true, allows the embedded content to change the URL of the parent window, but if missing or set to false, it restricts this navigation for security reasons. Unfortunately, we lack control over the HTML attributes of the playground iframe.
Is there someway this behavior can be changed?
Thanks!
The text was updated successfully, but these errors were encountered: