[
https://issues.apache.org/jira/browse/WICKET-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998282#comment-12998282
]
Martin Grigorov commented on WICKET-3471:
-----------------------------------------
This usecase is a bit strange to me - a component is enabled only when there is
a request.
checkUsability() is there to prevent usage of (e.g. clicking on)
disabled/invisible components. In real environment the browser cannot fire
event on such component.
I am not sure your use case can be supported in WicketTester. We either need to
remove the whole check or make this method protected so you can override it
locally to support your need.
> WicketTester checkUsability is called before the request has started
> --------------------------------------------------------------------
>
> Key: WICKET-3471
> URL: https://issues.apache.org/jira/browse/WICKET-3471
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.15
> Reporter: Emond Papegaaij
> Attachments: quickstart.tar.bz2
>
>
> For example, when clicking a link, the checkUsability method is called with
> the link before RequestCycle.onBeginRequest has been called. This causes
> tests to fail when, for example, the link has a security check that requires
> the request cycle. I've created a quickstart that demonstrates the problem.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
