[
https://issues.apache.org/jira/browse/WICKET-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Thomerson updated WICKET-1619:
-------------------------------------
Attachment: 1619.patch
Here is one possible way of fixing this. Two potential issues I see:
1 - setEnabled is being called on the links when they are added - this works if
someone calls PagingNavigator.setEnabled(boolean) when they are creating it,
but might not work if they override isEnabled and depend on some other
criteria.... not sure, I'd have to think about that more.
2 - I made changes to Link.isEnabled - they should be double-checked to make
sure that it's not going to cause other problems.
> PagingNavigator.setEnabled(false) doesn't work
> -----------------------------------------------
>
> Key: WICKET-1619
> URL: https://issues.apache.org/jira/browse/WICKET-1619
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.3
> Reporter: Sergey Derugo
> Attachments: 1619.patch
>
>
> 1. Create paging navigator PagingNavigator
> 2. call PagingNavigator.setEnabled(false)
> 3. navigator will be rendered as enabled, if click on any link ("1", "2" etc)
> - content of the data view will be changed.
> In many cases it's necessary disable navigator, for example, when user need
> to edit only single line of DataView other controls need to be disabled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
