JDK-7124395 : [macosx] Disposing a child Dialog returns focus and ability to a previously disabled parent Frame
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 7
  • Priority: P4
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: os_x
  • CPU: generic
  • Submitted: 2011-12-23
  • Updated: 2012-05-11
  • Resolved: 2012-05-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7u6Resolved
Related Reports
Relates :  
Description
http://java.net/jira/browse/MACOSX_PORT-265 submitted 2011/08/11 by Yuri Nesterenko
Create a Frame with a Button and it's child Dialog. Disable Frame. If you then dispose of the Dialog, Frame may become active, quite enabled, and focusable.
In the attached small example, Frame will be displayed with a Dialog and then disabled. Actually, frame.setEnabled(false) seems to have no effect at all, though. On other platforms, it's child Button also would became disabled but not in this port. Click a button in Dialog: it will dispose Dialog. If you click then the Frame's Button, the Frame will cheerfully gain focus, and Button fire an action event.

Comments
EVALUATION With a fix for 7124376 the issue is no longer reproducible: the button can't be clicked. Note that a disabled frame (f.setEnabled(false)) still can gain focus, even on other platforms (I've tested this on Windows.)
05-05-2012

EVALUATION I've verified with both JDK 8 and 7u4 latest builds, and the issue isn't reproducible: the button in the Frame is not clickable even after closing the dialog. Note, however, that the frame may still gain the focus even while the dialog is open. This looks like an issue with modality implementation on the Mac.
20-04-2012

EVALUATION Author: Yuri Nesterenko Date: 11/Aug/11 10:44 AM Build: b202 AWT_TopLevels/TopLevelEvents/Automated/WindowActivatedEventsTest02
23-12-2011