fix: Restore auto-close behavior for standalone flyouts

[mjgallag]

The basics

• I validated my changes

The details

Resolves

Fixes #10510

Proposed Changes

Fixes standalone flyouts with setAutoClose(true) staying open after dragging a block into the workspace.

Standalone flyouts have no category toolbox to handle closing on focus loss. WorkspaceSvg.onTreeBlur now falls back to the flyout's own autoHide method, which respects that setting.

Reason for Changes

• feat: Make toolbox and flyout focusable (roll forward) #8939 (12.0.0) introduced focus-based closing.
• fix: Make non-autoclosing flyouts stay open. #9245 (12.3.0) removed the direct flyout auto-hide call as redundant with toolbox handling. Standalone flyouts have no toolbox, but continued closing through the existing drag-time closing path.
• refactor!: Move responsibility for block creation out of flyouts #9610 (13.0.0) removed Flyout.createBlock() and its hideChaff() call, exposing the missing standalone-flyout focus handling.

Test Coverage

Added standalone flyout tests matching the existing toolbox focus tests, covering auto-close enabled and disabled.

[github-actions]

Welcome! It looks like this is your first pull request in Blockly, so here are a couple of tips:

• You can find tips about contributing to Blockly and how to validate your changes on our developer site.
• We use conventional commits to make versioning the package easier. Make sure your commit message is in the proper format or learn how to fix it.
• If any of the other checks on this PR fail, you can click on them to learn why. It might be that your change caused a test failure, or that you need to double-check the style guide.
  Thank you for opening this PR! A member of the Blockly team will review it soon.

[lizschwab]

Hi Michael,

Thanks for taking a look at this for us. I'm trying to replicate the issue you're describing but I don't see the behavior issue implied by the tests happening in the playground.

Usually we prefer that a fix is created against an issue. Please submit a bug with detailed steps to reproduce the issue that this change is meant to resolve, and then assign that issue to me so that I can take a look.

I do see that if I run your unit tests locally without your changes the Losing focus hides autoclosing flyout test fails, so it does seem to me that there's something going on here; I just want to be able to run the code before and after your changes to manually test it and see the behavior change.

Thanks,
Liz

Edited to add:

When I tested this in the playground, I did the following:

1. Drag a block out of the toolbox into the workspace
2. Open the toolbox flyout
3. Focus the block on the workspace (tried both clicking the mouse and keyboard navigation)

When that didn't work, I tried opening the toolbox and changing the focus from the console using the following code in the chrome devtools console:

Blockly.getFocusManager().focusNode(Blockly.getMainWorkspace().getTopBlocks(false)[0])

With both approaches the flyout was hidden as expected.

[mjgallag]

Hi @lizschwab, thanks for taking a look so quickly! See #10510 for more details and steps to reproduce. Doesn't seem I am allowed to assign to you :)

[lizschwab]

Beautiful, thanks! I was able to manually test this and confirm your fix is working correctly.