[
https://issues.apache.org/jira/browse/WICKET-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507912
]
Eelco Hillenius commented on WICKET-673:
----------------------------------------
It was a good idea to detach there anyway :)
> synchronize AbstractBehavior#isEnabled(Component component) with
> Component#isEnabled
> ------------------------------------------------------------------------------------
>
> Key: WICKET-673
> URL: https://issues.apache.org/jira/browse/WICKET-673
> Project: Wicket
> Issue Type: Bug
> Reporter: Eelco Hillenius
> Assignee: Eelco Hillenius
> Fix For: 1.3.0-beta2
>
>
> AbstractBehavior#isEnabled(Component component) currently returns true
> by default. Better would be:
> public boolean isEnabled(Component component)
> {
> return component.isEnabled();
> }
> Behaviors should be ignored when a component is not visible, but some
> components like TextFields for instance, can be disabled but still
> visible. A concrete case I have here is a disabled textfield with a
> datapicker attached, and the datepicker is still visible and worse,
> when you use it, you can change the value in the textfield.
> See also
> http://www.nabble.com/AbstractBehavior-isEnabled%28Component-component%29-tf3949139.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
