[13.0.0-beta.8] Consider focusing the workspace itself instead of first top block

[microbit-robert]

Check for duplicates

• I have searched for similar issues before opening a new one.

Description

Currently, when the workspace takes focus for the first time, focus is moved to the first block in the workspace if it exists. As noted in our user testing feedback, we found that when the first block in the workspace was focused, the output was harder to parse than when the workspace itself was focused. When the block is focused, the user gets a lot of information: the workspace region change and the block output. They often missed that they were now inside the blocks workspace as a result.

In addition, the screen reader hint is only output when the workspace takes focus. It is not output when the first block is focused - and if it were, it would be even more information for the user to take in. In MakeCode, the first workspace focus almost always lands on a block since new projects start with the onStart and forever blocks.

If we focus the workspace itself on first focus, both of these issues are addressed. If we are aligned on this change, the code change is also trivial, just return null here.

Reproduction steps

Priority

No response

Stack trace

Screenshots

No response

Browsers

No response

[maribethb]

Thanks, this makes sense, let's do it.

[maribethb]

For mutator workspaces, I think it does make sense to focus the first block, because mutator workspaces can never be empty, and the label for the mutator workspace is almost entirely redundant with the label for the group that gets focused immediately before you go to the workspace. So I'm going to make that change. We make the same exception for flyout workspaces.