JDK-4752911 : JInternalFrame's controlling buttons are not exposed
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.accessibility
  • Affected Version: 1.4.0
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2002-09-25
  • Updated: 2003-08-26
  • Resolved: 2003-08-26
Related Reports
Duplicate :  
JDK-4864304 - Improve memory consumption of Swing apps
Description
The 'minimize' 'maximize' and 'close' buttons of a JInternalFrame's frame
decoration should be exposed as accessible objects.

This can be reproduced in the SwingSet2 demo, using at-poke:-

Switch to the 'Internal Frames Demo' in SwingSet2.
Expand the widget tree in at-poke for one of the JInternalFrames.

You will be unable to find an object representation for any of
'minimize' 'maximize' or 'close'.
Comments
EVALUATION Reassigning to java/classes_swing since it involves a component look and feel issue (BasicInternalFrameTitlePane). The NoFocusButton class would need to be modified to return true for isFocusTraversable() and an AccessibleName would need to be assigned to each button. ###@###.### 2002-10-22 We could certainly add an AccessibleName to the buttons (I think that is easy), but most users would consider this a bug if we made the buttons focus traversable. As far as I can tell NONE of the window managers that exist today allow you to transfer focus to the widgets that represent these buttons. So, will adding AccessibleNames be enough? ###@###.### 2002-10-22 My suggestion is to not fix this bug since it would introduce a look and feel incompatibly like you've stated and the maximize, minimize and exit functionality is available by other means (e.g., from the keyboard and possibly menu). I'm CC'ing the bug submitter to make sure this is acceptable. And, no I don't think that adding an AccessibleName would be sufficient since users would not be able to navigate to the buttons. ###@###.### 2002-10-22 I'm moving to incomplete until we hear back from the submitter. ###@###.### 2002-10-23 As pointed out by Bill (###@###.###), this bug isn't about keyboard navigation. The controls in question must be exposed, in order to be useful to AT tools. For example, without these controls having their accessibility interfaces exposed, the Gnome AT tool, at-poke, does not see these buttons in it's accessible widget tree. While all other exposed widgets in the Java app under scrutiny by at-poke are actionable/their details viewed, a JInternalFrame's controls are not. ###@###.### 2002-11-05 I'll add the AccessibleName to those buttons. ###@###.### 2003-04-15 Transferring to the accessibility team to be reassigned to someone who knows more about this. ###@###.### 2003-08-11
15-04-2003