This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Testing on Orion Build 011002_2 on NT. Steps: 1. In explorer select a node 2. Type Shift+10, you see a context menu 3. Hit down arrow What should happen is navigation in the context menu. I see the system menu drop down instead. If you invoke the context menu via the mouse it works ok. P2 because this is an accessibility bug.
Additional information: appears to be a focus problem. Typing F10 (again without shift augmentation) after context menu appears will switch focus to context menu and then arrow keys work.
I think that it is focus problem too.
Dusan, as this is accessibility bug, can you look at it? We here have no knowledge about how shift+f10 works or how should it work. Thanks.
Hi Dafe, Shift-F10 do the same as the the mouse right click, it means opens pop-up menu. This is not *only* accessibility bug, this behavoir is standard in all Java applications and have to work. Assigning back. QA: please, try to avoid assigning any new bug to the UI team, without prior consultation with us. Thanks.
Attaching 'A11Y' keyword.
Thanks for explaining - however I still see it as ui/accessibility/explorer bug, definitely not window system as winsys don't have any control over context menu inside explorer. So, changing component and subcomponent to explorer. Last note - I don't understand your last comment - *I* reassigned this bug to you, not QA. Is UI team so special that we can't assign bugs to UI as usual....heh? I strongly disagree.
It seems to be working now. Closing the issue. Probable fix: core/.../core/NbMainExplorer.java [1.82]
Reopened because the probplem happens in W2K dev3.3 #20011011 Instead of moving down the menu the top (netbeans) window menu pops up. (restore, move, size .... close)
Well is seems to be problem with Win only. Maybe focus manager. Since it is a11y bug, assigned to UI.
Swing by default does not allow you to navigate popup menu using keyboards at all. What we are doing in NB is already an attempted workaround (focus manager hack) which seems not working in all cases. We don't want to work around A11Y bugs in JDK => lowered prio to P3.
Assigning to informal AWT/Swing category owner. Or should we assign it to Dafe?
not fixable. JDK issue. On Windows Shift-F10 jumps to the System menu box. You can override it but only by using native code. JDK does not do it for us. Either choose another shortcut to invoke context menu or not implementing invoking popup menu on Windows
Let's keep this open until a JDK bug has been filed and accepted as valid by the JDK team. Changing to P1 since accessibility is totally broken by this bug... product will not be accessible.
Okay I've found a workaround for JDK 1.4. JDK 1.3.1 is probably hopeless, we won't fix it. Fixed in cvs trunk, patch for release33/orion_fcs attached soon. Also added 3.3.2_CANDIDATE keyword
Created attachment 5244 [details] Diff against release33/orion_fcs branches
Created attachment 5245 [details] Binary jar patch for orion_fcs/release33, put in <ide>/lib/patches
patch verified in [orion_CE](20020401) && [jdk1.3.1](03)/[jdk1.4](fcs) on Win2K/Solaris5.8. It seems like it works fine now. Thanks Trung.
The proposed patch has been verified. Can you please start working on integration into orion_fcs?
integrated into orion_fcs branch
verified in [orion_fcs](020410_2)
Resolved for 3.4.x or earlier, no new info since then -> closing.