Playground embeds WordPress site within iframe without including the allow-top-navigation HTML attribute

[miriamelementor]

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!

[bgrgicak]

I tested this with allow-top-navigation but it didn't resolve the problem. When I fully removed sandbox attributes clicks started working, but this isn't an option for us. It also ended up on an error page (see screenshot).

[bgrgicak]

@miriamelementor in case we can't resolve this before WCEU, we could disable the onboarding flow and open a different page.
In general I think that it would be a good idea to disable it for the puzzle app because it takes over the admin UI which hides the fact that multiple pieces were scanned.

[adamziel]

@miriamelementor there's multiple places in WordPress where a link or a form uses target="top". One of the intentions behind the current set of iframe attributes is to protect the user from reloading the website as that would destroy the running Playground – it lives only as long as the top-level page. Could Elementor onboarding be adjusted to avoid taking over the top level page?

[bgrgicak]

Great catch @adamziel I missed this.

[miriamelementor]

@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.