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.

Bug 17958 - [windows only] Cannot move in popup menu in explorer after Shift+F10
Summary: [windows only] Cannot move in popup menu in explorer after Shift+F10
Status: CLOSED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: _ ttran
URL:
Keywords: A11Y
: 21264 21868 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-11-22 09:51 UTC by Jaromir Uhrik
Modified: 2008-12-22 23:53 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jaromir Uhrik 2001-11-22 09:51:35 UTC
[200111220100; the last jdk14]
Steps to reproduce:
1.Invoke popup menu on some node in explorer by Shift+F10
2.Try to move in this menu by keyboard arrows 
3.The "system" popup menu for explorer window will popup instead
Comment 1 Marian Mirilovic 2001-11-22 10:32:09 UTC
[jdk1.4](87)

NOT on another OS/ nor [jdk1.3.1](01)

Seems like only Windows issue, I cannot reproduce it on Solaris 5.8
(CDE) or Linux.
Comment 2 Marian Mirilovic 2001-11-22 10:34:39 UTC
cc-ing me
Comment 3 _ ttran 2001-11-22 21:08:18 UTC
Shift+F10 is a system shortcut on Windows.  It means if the app
doesn't swallow the key event, the behavior you described will happen.
 Unfortunately we cannot do much in java code.  This must be handled
by JVM.

This issue is a duplicate of a bug report I closed recently as WONTFIX.

The workaround for this problem is not to use Shift+F10 to invoke
context menu.
Comment 4 Marian Mirilovic 2001-11-23 08:35:44 UTC
Trung, it seems that this is Focus problem on windows. If you invoke
popup menu ( without any problems ) by hitting Shift-F10 and you
aren't able to select item inside, this means that popup isn't Focus
owner, or I am at fault?

If you do these steps :
- select node in Epxlorer
- hit Shift-F10
-> now it's impossible select some item by hitting Up/Down , and this
action (hit Down/Up) invoke window system menu
- but if you before hitting Down/Up hit Tab and next Down/Up it works
fine !!!


Another question:
Haw can it be possible select item by Down/Up in the Source Editor ?

I don't want reopen this issue, until we make consensus. Trung?
Comment 5 Jan Zajicek 2001-11-26 13:15:12 UTC
CCing me.
Comment 6 Marian Mirilovic 2001-11-30 15:45:15 UTC
After my & Trungs consensus, I reopen this issue, because fix is
needed for accessibility of IDE on Windows. 
Comment 7 _ ttran 2001-12-18 23:44:57 UTC
I am able to produce it even on JDK 1.3, so it's not jdk 1.4 specific.

This behavior is 100% reproducible if the focus is set to one of the
tab handle ("Filesystems", "Runtime",...).  Tab handles are not
focusable in editor windows.  That's the reason why it "works" fine there.

My previous analysis is still valid

> Shift+F10 is a system shortcut on Windows.  It means if the app
> doesn't swallow the key event, the behavior you described will happen.

You can verify it by displaying an empty JFrame and press F10 or S-F10
then <Down>.

This one is not fixable (without an ugly hack at least).  It was not
an issue in the past because tab handles were not focusable, which was
 considered A11Y bug.  That bug was fixed and the side effect of that
is this one

I am resolving this one as WONTFIX, otherwise we'll have to rollback
the fix to make tab handles in Explorer focusible.

Comment 8 _ ttran 2001-12-18 23:49:49 UTC
see my previous comments on why this one cannot be fixed
Comment 9 Jaromir Uhrik 2002-01-18 13:44:18 UTC
OK I will use Tab after Shift-F10 to be able move in popup menu.
Comment 10 Marian Mirilovic 2002-03-06 17:58:30 UTC
*** Issue 21264 has been marked as a duplicate of this issue. ***
Comment 11 David Simonek 2002-05-28 16:48:35 UTC
*** Issue 21868 has been marked as a duplicate of this issue. ***
Comment 12 David Simonek 2002-05-28 16:49:10 UTC
x
Comment 13 David Simonek 2002-05-28 16:50:53 UTC
changing resolution to WORKSFORME, as everything seems to be ok on
latest Hopper (1.4.1) build. It seems that code on JDK side changed so
that it works ok now.
Comment 14 Jaromir Uhrik 2002-05-29 07:56:56 UTC
Verified - works OK [200205280100; last Hopper]
Comment 15 Quality Engineering 2003-07-01 16:18:41 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.