Community
Participate
Working Groups
Build 20020228 - choose Help -> Help Contents -> Platform Plug-in Developer Guide -> Programmer's Guide -> JFace UI Framework -> Viewers. - click on JFace UI Framework - it collapses The auto-expand is OK, but auto-collapse is usually not what the user wanted. In this case, I still wanted to see the topics under JFace. It should use double-click for collapse, or perhaps single click but only if the selection is not changing.
In general, there is a problem with some container nodes having topics, and some not. This makes collapsing/expanding of container nodes interfere with showing their content when it exists. Personally, I prefer a simple, predictable behavior, as opposed to adding rules, but I think it would be better to also get Julian's input on this, before making any changes.
In the new help redesign we also use plus/minus icons. Perhaps we should collapse only when clicking on the minus icon.
*** Bug 17283 has been marked as a duplicate of this bug. ***
Please bump up priority. I think this is a major usability problem with Help. Thanks.
Increasing priority as per Nick's comments. There is still the accessibility issue: what are the keys to expand/collapse nodes (currently Enter does the dual job of select/collapse/expand), that does not conflict with the user. Keyboard navigation aside, I had a prototype that worked as follows: - mouse click on plus/minus expands/collapses the node - mouse click on label displays the topic - double click on label exapands/collapses the topic The issue is really what keys to use, as arrows are out of questions (browser uses them) and double click has no keyboard equivalent.
One of the major problems with V1 navigation was that single-clicking on a node would not expand it, so users weren't finding stuff underneath it. I (on behalf of the users) would hate to see us go back to that. I know it's complicated, but consider the following instead: - single-clicking on a closed node will expand it - single-clicking on an open node would NOT collapse it, but would show its content - double-clicking on an open node would collapse it. Or, if that's impossible, only clicking the minus symbol would collapse it; no amount of clicking on the label itself would close it.
Kari's comment reflects what Nick said when he opened the bug, so I think we should try to implement it. I will need to see how keyboard navigation will work.
I implemented a tree behavior as described Kari's comment. one can also use the left/right keys to expand a node.
