Block Inserter Panel Does Not Close After Interaction on Mobile/Tablet web editor

[Kallyan01]

Description

When using the Gutenberg editor on mobile or tablet browsers, the block inserter panel remains open after performing actions such as dragging and dropping or clicking on a block. This behavior is not ideal as it obstructs the editing canvas and disrupts the user experience.

VID_20250121001326.mp4

Expected Behavior

The block inserter panel should close automatically once the user interacts with the block list (e.g., after dragging and dropping or clicking on a block). This would improve usability by reducing distractions and providing a smoother editing experience.

Step-by-step reproduction instructions

1. Open the Gutenberg editor on a mobile or tablet browser.
2. Open the block inserter panel.

3. Attempt to:

• Drag and drop a block to the canvas.
• Click on a block to add it to the editor.
• Observe that the block inserter panel remains open after completing the action.

Screenshots, screen recording, code snippet

Environment info

• Wordpress 6.8
• Gutenberg 20.0.0
• Env Type : Mobile and Tablet Devices

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

• Yes

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

• Yes

Please confirm which theme type you used for testing.

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

[Kallyan01]

@ellatrix @bjtitus @Mamaduka can you look into this issue and confirm ?

[Mamaduka]

I thought this was resolved. @jeryj, we were discussing something similar very recently.

[Kallyan01]

@Mamaduka Checked the latest trunk, the bug still exist ! can you mention the PR / Issue which resolved the issue ?

[jeryj]

@Mamaduka - I don't recall working on closing the inserter after mobile/tablet interactions. The closest thing to this I remember is working on the useZoomOut hook to not engage on tablet/mobile.

[Mamaduka]

I think the issue in question and PR are similar, but not the same - #67339 (comment).

Sorry for the confusion, @jeryj!