How to reproduce:
-Right click on any node in the Project or Filesystem tree,
-Netbeans property sheet window/dialog appears (with name "**** - Properties")
-try to start tab traversal of the components on this window by pressing "tab" key
-none of the components can be reached
However, click on one of the properties and then press the tab key, all the
components can be traversed from them on.
The fix could be, put the default focus on the first property in the properties
I think, this is not a bug. When the property sheet window/dialog appears, the
PropertySheet table has focus. When a user wants to move out from the
PropertySheet table, Ctrl-Tab must be pressed. PSheet (description area below
PropertySheet table) gets focus after that. A user can use Tab or Ctrl-Tab now
for focus movement to Close button and to PropertySheet table (in cycle). When a
user wants to move from the PropertySheet table, Ctrl-Tab must be pressed again.
When the PropertySheet table has focus and user wants to move inside the
PropertySheet table, Arrow-Down or Arrow-Up must be pressed. When a table row
has focus, Tab or Arrow-Down can be used for movement to next row and Shift-Tab
or Arow-Up can be used for movement to previous row.
Could somebody from openide evaluate my opinion? Thanks.
It would be a nice enhancement if the first property has a focus after the first
invocation. So confusion with TAB would disappear + maybe another minor tuning.
Also I'm not sure if there is not any behaviour required by HIE.
I believe that the behaviour described by Petr is clear and intuitive enough -
I'm also using almost keyboard only.
Feel free to reassign Petr ;)
Petr's evaluation is correct. Ctrl-Tab must be used, because the property sheet
table component consumes Tab. This behavior is by design.
Ctrl+Tab seems to me like a workaround. But I agree with mkrauskopf - to have a focus at the first property.
Sorry, I have wrongly written Ctrl+Tab instead of "Tab". So that to workaround this bug just push "Tab" when new propertysheet is opened.
After former changes in code it seems to be fixed now - I cannot reproduce this problem in latest release 6.9.1. Marking issue as resolved.