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 21868 - Explorer Context menu produced via Shift+F10 requires Escape key be pressed twice to dismiss
Summary: Explorer Context menu produced via Shift+F10 requires Escape key be pressed t...
Status: CLOSED DUPLICATE of bug 17958
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Windows 3.1/NT
: P3 blocker (vote)
Assignee: David Simonek
URL:
Keywords: A11Y
Depends on:
Blocks:
 
Reported: 2002-03-26 02:00 UTC by ssffleming
Modified: 2008-12-22 21:38 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ssffleming 2002-03-26 02:00:12 UTC 
I am making this P2 because it impacts accessibility

Seen in EE trunk build 020315 running on NT 4., JDK 1.4

Steps to reproduce:
1.  Open explorer and select a node
2.  Open context menu by typing Shift + F10.
3.  Type escape key...nothing happens
4.  Type escape key again...context menu goes away

Seems to happen consistently this way

Is there a keyword for A11Y I should set...not sure how sorry.
Comment 1 Marian Mirilovic 2002-03-26 09:13:53 UTC 
I am sorry Steve but I cannot reproduce it on 020307/ SOlaris/ JDK1.4,
but I am going to try on NT.

A11Y is right keyword.
Comment 2 Marian Mirilovic 2002-03-26 09:21:33 UTC 
Steve is right, this happens me only on Win NT.
It seems like root of this problems is the same as for issue 17958
(Cannot move in popup menu in explorer after Shift+F10 - because popup
menu isn't focused in this moment, after Tab it is).

I am closing this one WONTFIX, see Trungs comments in issue 17958.
Comment 3 ssffleming 2002-04-08 17:47:10 UTC 
Hi Marian,

I'm not understanding why the won't be fixed...I would suggest following
Trung's earlier approach for working on a JDK 1.4 only fix.  I can see
downgrading this bug based on the fact that there's a workaround, but
I think this needs to be done in the overall context of "how are we
doing with keyboard accessibility?".  My view is we need to at least get
reasonable keyboard accessibility on JDK 1.4...  For now I'll knock this
one down to P3.

So the net is from a QA perspective that I'd like us to start accumulating
bugs in case we need to justify some major rewrite of the focus/keyboard
handling code in NB as a way of getting them all fixed if it is too hard
to fix them with the current codebase.
Comment 4 David Simonek 2002-05-28 16:48:36 UTC 
This is really duplicate of 17958, caused by problem that Trung
mentions in 17958 eval.
Btw, it works ok now with latest 1.4.1 for us, see 17958 comments.

*** This issue has been marked as a duplicate of 17958 ***
Comment 5 Jaromir Uhrik 2002-05-28 17:08:14 UTC 
Verified -works fine [build #20022805..., jdk 1.4.0 (final 
release) and also last jbuild of dk141, WinNT and Win2K].
Comment 6 Quality Engineering 2003-07-01 16:20:05 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.