You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2014/08/06 12:09:12 UTC

[jira] [Resolved] (WICKET-4551) Enable components underneath disabled components

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

Martin Grigorov resolved WICKET-4551.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 7.0.0-M3
         Assignee: Martin Grigorov

With Wicket 7 it will be possible to contribute the JS of an Ajax behavior by overriding canCallListenerInterface().

I think the fix is safe to be ported to 6.x but since there is a workaround I prefer to test it for a while in 7.x and port it to 6.x only by request. 

> Enable components underneath disabled components
> ------------------------------------------------
>
>                 Key: WICKET-4551
>                 URL: https://issues.apache.org/jira/browse/WICKET-4551
>             Project: Wicket
>          Issue Type: Wish
>          Components: wicket
>            Reporter: J. Lind
>            Assignee: Martin Grigorov
>            Priority: Minor
>             Fix For: 7.0.0-M3
>
>         Attachments: AlwaysOnAjaxLink.java, quickstart.zip
>
>
> I would like to force some child components to be enabled regardless of the state of the parent component. For example, I would like to have an ajax link within a form that is enabled allthough the form itself is disabled. A suggested solution to override org.apache.wicket.markup.html.link.AbstractLink#isLinkEnabled() and
> org.apache.wicket.Component#canCallListenerInterface(Method) did not work (see quickstart). Method Component#isEnabledInhierarchy might do the trick but is marked final.



--
This message was sent by Atlassian JIRA
(v6.2#6252)