Why do toolbar and tabs trigger focus mode?

[Sidnioulz]

I've read #1339 and

nvda/source/browseMode.py

Lines 386 to 388 in 23b4992

	while obj and obj != self.rootNVDAObject:
	if obj.role == controlTypes.Role.TOOLBAR:
	return True

, and understand the behaviour is intentional.

But I'm wondering if there isn't a better way to provide Left/Right and Up/Down navigation in these elements without switching entirely to focus mode. This switch causes landmark navigation shortcuts to break, making it rather disruptive in web apps where a landmark only contains a toolbar.

Am I misunderstanding the constraints that cause focus mode to be required? Is this a compromise to ensure arrow navigation works because there isn't an in between between focus and browse modes?

[seanbudd]

They have focusable descendants and this situation is what focus mode is designed for

[Sidnioulz]

Thanks for the reply. I suppose I was expecting to control myself when NVDA changes modes, rather than it do it on its own. Is it something that I can configure as a user?

[seanbudd]

Yes you should be able to change it with the setting "Automatic focus mode for caret movement"

[Sidnioulz]

Thanks! I'd missed the option 🙏