Hi,
If the page is not unlocked then it is a bug.
But it is strange that no one faced it before. This code is in use since
Wicket 1.5.0.
On Tue, Aug 13, 2019 at 7:38 AM Andrew Kondratev
wrote:
> Hi!
>
> My colleague noticed some dodgy behavior, which I think could be a bug.
> Just asking here
Hi!
My colleague noticed some dodgy behavior, which I think could be a bug.
Just asking here if it's known, befor I try to create a quickstart or PR.
* page is rendered
* user interacts with a page causing ajax request (clicking checkbox)
* the wicket PageAccessSynchronizer locks, renders and
