Windows accessibility: focus bug in "Device" category of Preferences dialog (FIXED)

[Scottsdale]

Hi,

In Windows builds, focus gets stolen the first time you use the keyboard to navigate to "Device" in the category tree of the Preferences dialog.

Reproduction steps:

1. Open the Preferences window, select any category other than "Device" and hit OK to close the dialog (bear with me, this stage is just to set you up for success in next steps).

2. Reopen the Preferences dialog, then use either UpArrow or DownArrow to navigate through the categories until you reach "Device".

3. Notice how when you reach the Device category, focus gets automatically redirected to the "Audio system" combo box? That's the bug.

4. Keep Preferences open, move back to the category tree, and use your keyboard to move away from the "Device" category.

5. Use the keyboard to return to the "device" category. Notice how this time, focus doesn't jump anywhere? That's the expected behaviour I reckon, seeing as that's how all other categories behave.

Not a showstopper, but a UX oddity that I'd like to get squashed if poss.

Cheers,

Scott

[Overlord25]

Yes would definitely be good to squash this one, it's not a biggie now but for newbies it can cause confusion by inadvertently changing the default audio interface when tabbing and arrowing around the preferances dialogs

[Kara Louise]

Yes, it’d be great to finally get this one squashed.

[Castle Starter]

I'd like to see this fixed. It certainly happens and is inconvenient and can also mean you change the settings inadvertently which can be pretty crucial for this bit of the preferences.

[Straylight]

Yep. For new users particularly, this can certainly throw you as you're adjusting settings. You think you're cursoring up and down in the tree view but will actually be changing your device settings.

[Scottsdale]

Just re-tested - this is fixed in 6.05. Many thankyous!

[Scottsdale]

This bug is present again in 6.09. May have reappeared even sooner (I was lagging on 6.05 for a while longer than usual).

[Justin]

I don't think it was fixed in 6.05, was there a changelog line that mentions it?

Anyway taking a look now.

[Scottsdale]

Originally Posted by Justin

I don't think it was fixed in 6.05, was there a changelog line that mentions it?

I don't recall seeing it in the changelog no, but it started behaving properly in 6.04+dev0224, right around the same time as when Kenny fixed another bug I'd reported (t=231969), so I assumed he'd also fixed this.

Does that help narrow it down any?