[
https://issues.apache.org/jira/browse/WICKET-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pedro Santos resolved WICKET-4060.
----------------------------------
Resolution: Not A Problem
It is an expected behavior for visioned pages. If the page's first version has
the ajax link enable, and if user navigates back to it, he will be able to
click its ajax link.
Karel, consider to move the enabled/enabled logic to Component#onConfigure, so
at any moment it will be correct, since this method is called before every
component rendering.
> Disabled AjaxLink calls onClick()
> ---------------------------------
>
> Key: WICKET-4060
> URL: https://issues.apache.org/jira/browse/WICKET-4060
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.0
> Environment: all
> Reporter: Karel Cabel
> Assignee: Pedro Santos
> Priority: Minor
> Attachments: WICKET-4060.zip
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> 1) Render AjaxLink and copy its URL
> 2) Render again with disabled AjaxLink (there will not be any URL on client)
> 3) Enter URL from 1) to browser and go -> it calls onClick() on server
> This is because AjaxLink uses behavior that doesn't check disabled state on
> binded component (it checks it for rendering only).
> However normal Link works OK and doesn't call onClick().
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
