Yeah, this is a known issue. It is fixed in 2.0, the fix will probably
be backported to 1.x at some point.
-Matej
De Soca wrote:
Hello,
just wondering if this a bug or a feature.
Using one of the AjaxLink samples included in the Wicket examples, it seems
that the setEnabled flag is
Okay. Thanks.
Erik van Oosten wrote:
Looking in the code of AjaxLink I see no special code for
enabled/disabled state.
If it fits what you need, you could try AjaxFallBackLink.
Otherwise try to extend AjaxLink and override the method
renderComponentTag in which you remove the onclick
Hello,
just wondering if this a bug or a feature.
Using one of the AjaxLink samples included in the Wicket examples, it seems
that the setEnabled flag is ignored for AjaxLinks.
i.e ajaxLink.setEnabled(false);
Seems to have no effect.
Is this a feature or defect etc?
Thanks.
--
View this
Looking in the code of AjaxLink I see no special code for
enabled/disabled state.
If it fits what you need, you could try AjaxFallBackLink.
Otherwise try to extend AjaxLink and override the method
renderComponentTag in which you remove the onclick attribute from the
tag. (Don't forget to call
