Tabbing to the flyout doesn't select a block or allow arrow navigation

[microbit-matt-hillsdon]

Tabbing to the flyout doesn't select a block or allow arrow navigation. Using arrow right from the toolbox does.

I think this is the distinction between the flyout having focus and the its nested workspace having focus, but that's not a user visible distinction.

Feels extra broken in the flyout-only scenario.

[BenHenning]

I'm not seeing the issue described here, other than the auto-selection not working with tabbing. Arrow navigation is working for me, however. See videos:

Screen.recording.2025-05-19.11.32.22.AM.webm

Tabbing/shift tabbing with toolbox Flyout

Screen.recording.2025-05-19.11.31.21.AM.webm

Tabbing and using 'T' with permanent Flyout

Am I maybe misunderstanding the repro? Note that this is on Chrome in case the behavior is different on Firefox or Safari.

We do need to fix the auto-selection issue for Flyouts but I was more concerned with arrow navigation being broken. I can't seem to get the Flyout into that broken state.

In case it's relevant, RaspberryPiFoundation/blockly#9062 fixed an issue that caused problems specifically with variables, but I didn't test it with the permanent Flyout case so perhaps that is what broke arrow navigation in your testing?

[microbit-matt-hillsdon]

I think something has changed that fixed this but not sure what!

It reproduces with 12.0.0 tabbing to the flyout then pressing down. It doesn't work on the deployed demo or if I build locally with released v12 but works if I npm link blockly's develop branch as of 135da402ef0035ce5a44d4a5d5d73d576e92bc82 (not tried other commits).

This can be closed unless you think it's worth tracking down the change.

[BenHenning]

I think something has changed that fixed this but not sure what!

It reproduces with 12.0.0 tabbing to the flyout then pressing down. It doesn't work on the deployed demo or if I build locally with released v12 but works if I npm link blockly's develop branch as of 135da402ef0035ce5a44d4a5d5d73d576e92bc82 (not tried other commits).

This can be closed unless you think it's worth tracking down the change.

Ah, I'm nearly certain that this was fixed by RaspberryPiFoundation/blockly#9062 then since that didn't make it into v12. I'll do a before-and-after check to verify.

[BenHenning]

So I did spend some time trying to root cause the fix, and I'm having difficulties. For some reason the behavior isn't consistent across page loads, so I'm going to keep this open as part of an ongoing investigation to understand what's happening here.

[BenHenning]

Apparently I need to be more noticeable when I'm using the incorrect test environment. There are not inconsistencies, just me using the wrong page. :)

Can confirm #9062 fixed this, so going ahead and closing.