Spacer block, when used as Grow(Fill) or Fit, will prompt a user about unsaved changes when navigating away, even when no unsaved changes

[MadtownLems]

Description

When you leave the Post Editor of content that contains a Spacer Block set to either Grow (previously Fill) or Fit, the browser will warn you about losing unsaved changes, even if you haven't changed anything. The issue does not impact Spacer Blocks that have a Fixed height.

Step-by-step reproduction instructions

1. Create a new Post.
2. Insert a Stack.
3. Insert a Spacer within the Stack.
4. Set it to Grow.
5. Publish.
6. Go back to your All Posts list.
7. Return to editing the Post.
8. Make no changes, but navigate away.
9. See that you were warned about unsaved changes (even though you didn't make any)

Screenshots, screen recording, code snippet

No response

Environment info

WordPress 6.6.2 and WordPress 6.7. Theme: Twenty Twenty Four (and others). No Gutenberg plugin.

Please confirm that you have searched existing issues in the repo.

• [x] Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

• [x] Yes

Please confirm which theme type you used for testing.

• [x] Block
• [ ] Classic
• [x] Hybrid (e.g. classic with theme.json)
• [ ] Not sure

[Mayank-Tripathi32]

Hello,

Thank you for reporting this bug.

I have verified that the issue occurs with grow and fit, but it works fine with fixed width. I’ll now investigate possible solutions.

Thanks!

[Mayank-Tripathi32]

I’ve identified the problem—it originates from the useEffect running on load and updating attributes:

if (  isFlexLayout && ( selfStretch === 'fill' || selfStretch === 'fit' )) {

    if ( inheritedOrientation === 'horizontal' ) {
        setAttributes( {
            width: undefined,
        } );
    }  else {
        setAttributes( {
            height: undefined,
        } );
    }
}

I’ll investigate further to determine whether this can be removed or if additional checks are needed.

[Mayank-Tripathi32]

I’ve identified the problem—it originates from the useEffect running on load and updating attributes:

if ( isFlexLayout && ( selfStretch === 'fill' || selfStretch === 'fit' )) {

if ( inheritedOrientation === 'horizontal' ) { setAttributes( { width: undefined, } ); } else { setAttributes( { height: undefined, } ); } } I’ll investigate further to determine whether this can be removed or if additional checks are needed.

I believe adding a check && width !== undefined resolves the issue. I’ll proceed with opening a PR to address this.