JDK-4301871 : JComponent doc should note that setEnabled(false) will not disable child comps
  • Type: Bug
  • Component: docs
  • Sub-Component: guides
  • Affected Version: 1.3.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 1999-12-26
  • Updated: 2000-07-10
  • Resolved: 2000-07-10
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.
Other
1.4.0 betaFixed
Related Reports
Relates :  
JDK-4177727 - propagating disEnabled "event" to all children
Description
Many developers (understandably) assume that disabling a JComponent will also
disable its children, since a JComponent is a Container.  This is the subject
of Swing bug # 4177727, among others.

Since calling JComponent.setEnabled(false) does not currently ensure that its
children's setEnabled(false) methods will also be called, we should document
this behavior explicitly.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic merlin-beta FIXED IN: merlin-beta INTEGRATED IN: merlin-beta
14-06-2004
EVALUATION Fixed for merlin. sharon.zakhour@eng 2000-06-21
21-06-2000