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 2010/11/14 19:47:17 UTC
[jira] Resolved: (WICKET-3164) executeAjaxEvent in WicketTester
works although Component is not enabled
[ https://issues.apache.org/jira/browse/WICKET-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-3164.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-M4
1.4.14
Checks added with r1035045 (1.4.x) and r1035041/1035044 in 1.5/trunk
> executeAjaxEvent in WicketTester works although Component is not enabled
> ------------------------------------------------------------------------
>
> Key: WICKET-3164
> URL: https://issues.apache.org/jira/browse/WICKET-3164
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.10
> Reporter: Frank Klein Koerkamp
> Assignee: Martin Grigorov
> Fix For: 1.4.14, 1.5-M4
>
>
> When Component is disabled the executeAjaxEvent still works. Because it's not checking if Component is enabled.
> But the event attribute is not rendered to the component if it's disabled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.