-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 1.3.0
-
Component/s: docs
-
beta
-
generic
-
generic
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.
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.
- relates to
-
JDK-4177727 propagating disEnabled "event" to all children
-
- Open
-