Annoying automatic focus box without using the keyboard

[quietrobot]

trafficstars

Describe the bug

I know this has been happening for a long time, but I would like to know if there are plans to fix it. Inconsistently, in certain apps and menus, the white focus box automatically appears (without using the keyboard).

Steps to reproduce the bug

For example when opening the sound recorder or the sound mixer from the taskbar.

Expected behavior

This box should only appear when using the Tab key to move around the interface with the keyboard.

Screenshots

NuGet package version

None

Windows version

Windows 11 (22H2): Build 22621

Additional context

No response

[github-actions[bot]]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one. Thank you!

Open similar issues:

• The focus rectangles are really annoying and look bad (#5633), similarity score: 0.76
• Elements in custom TitleBar see their focus border disappear partially or completely when resizing app (#7785), similarity score: 0.71

Closed similar issues:

• TextBox in a Flyout does not take focus (#8614), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[quietrobot]

@niels9001 I didn't remember that I had already commented on this in 2021, there is still no solution? thanks!

[kmgallahan]

Inconsistently, in certain apps and menus

The focus rect appears when you launch an app using the keyboard, such as by opening start, typing whatever, and hitting enter. If you click instead the box does not appear. The assumption is that you plan to continue using the keyboard. I don't like the behavior, but that is how it works.

[quietrobot]

@kmgallahan That would be understandable, but it just happens without using the keyboard. I updated the post to make it clear.

[quietrobot]

@codendone any news about this bug?

[codendone]

@quietrobot This bug is currently sitting on someone's backlog. No ETA available.

[quietrobot]

Thanks @codendone for your response. It is a bug that has been going on for several years, I hope they can find a solution. Thanks team.