You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2010/01/17 19:39:54 UTC

[jira] Resolved: (WICKET-2664) CheckBoxMultipleChoice should use isEnabledInHierarchy()

     [ https://issues.apache.org/jira/browse/WICKET-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juergen Donnerstag resolved WICKET-2664.
----------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.5-M1)
                   1.4.6
         Assignee: Juergen Donnerstag

applied to 1.4. 

1.5 looks different, without any call to isEnabled()

> CheckBoxMultipleChoice should use isEnabledInHierarchy()
> --------------------------------------------------------
>
>                 Key: WICKET-2664
>                 URL: https://issues.apache.org/jira/browse/WICKET-2664
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.4.1
>            Reporter: Craig McIlwee
>            Assignee: Juergen Donnerstag
>             Fix For: 1.4.6
>
>
> ... instead of isEnabled() when rendering.  This will make it consistent with all other form components, otherwise a call to setEnabled(false) on a form will disable all components except the CheckBoxMultipleChoice which requires special handling at the moment.
> FYI, I posted this to the mailing list and there were no objections or reasoning for the current behavior
> http://www.mail-archive.com/users@wicket.apache.org/msg46303.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.