Fix: Guard block selection when iframe isn’t in Gutenberg #8189
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When GiveWP’s Sequoia template runs inside an iframe on sites built with WP Bakery, the iframe isn’t wrapped in a Gutenberg .wp-block, so the block selection click handler throws. This PR adds safe checks for the frame element, .closest, and a valid data-block before dispatching block selection. That prevents errors in non-Gutenberg contexts while preserving the editor behavior when the block exists.
Affects
Sequoia template editor click handling for block selection in form.js.
Testing Instructions
Load a Sequoia form inside the block editor; click inside the form and confirm the block still selects.
Load the form on a WP Bakery page (no .wp-block ancestor) and confirm no JS errors.