Re: [orca-list] Default behavior for quick key toggling of focus mode is changed

[Joanmarie Diggs <jdiggs igalia com>]

Hey Attila.

On 08/16/2014 01:26 AM, Hammer Attila wrote:

> I tested little the newest changes.
>  When I using orca modifier+TAB or orca modifier+shift+TAB keystrokes to
> jump between form fields Orca not activating focus mode automaticaly.
> This is right?

Yes. Focus mode by default is no longer automatically enabled when you
use structural navigation commands to navigate amongst form fields. If
you look at the recent threads on the mailing list, nearly everyone said
things like "I want to use E to quickly jump from entry to entry until I
locate the one I want to fill out." If you don't like the default, you
can always configure it so that focus mode is automatically toggled on
for you.

The other thing to keep in mind is that Orca + Tab is the official,
default keybinding for structural navigation by form field. If you don't
change that keybinding, then it does seem like Orca + Tab is different
from using E. But you could rebind Orca + Tab to F, so that F moved you
to the next form field. If you did that, what should happen if you
landed in an entry and pressed F again? All structural navigation
commands need to be treated the same way. What that way is is up to you.
But whatever you choose for E is going to be the same behavior you see
with Orca + Tab when you move to an entry.

> When I using m or SHIFT+M keys to jump between landmarks, focus mode not
> activating automaticaly. This is right?

Almost certainly. Because landmarks are typically not form fields in
which printable character keys do things.

The auto-triggering of focus mode happens when:
1. You have chosen a setting to automatically toggle focus mode. This
   can be configured separately for caret nav and structural nav.
2. You have used a command in the group of settings for which you have
   enabled automatic toggling of focus mode (i.e. you used a structural
   nav command and have enabled automatic mode changing for structural
   nav commands).
3. As a result of that command, you are now on something that requires
   a mode switch. You need focus mode to interact with entries and
   combo boxes and list boxes and menus and things like that. You
   do not need focus mode to interact with push buttons and check boxes,
   etc.

So in answer to your original question regarding M and Shift+M: What
setting do you have for structNavTriggersFocusMode? If you didn't change
your orca-customizations.py and do have the latest master, then the
value you have for structNavTriggersFocusMode is False and it should not
be triggered. If you did change your orca-customizations.py to make the
default value for structNavTriggersFocusMode and you pressed M or
Shift+M, then focus mode should be triggered if what got focus is
something like an entry or a list box or a combo box or a menu.

I hope this helps clear things up.
--joanie