I meant for the blocking Button, i also remember implementing this from
time to time, so i wondered if there was a general solution to this.
Johannes
On 2019-12-31 15:48, Ernesto Reinaldo Barreiro wrote:
> Do you mean for the blocker thing? Or for login errors? Or both?
>
> Happy new year to all.
Do you mean for the blocker thing? Or for login errors? Or both?
Happy new year to all.
On Tue, Dec 31, 2019 at 4:07 PM Johannes Renoth
wrote:
> Hi Ernesto Reinaldo Barreiro ,
>
> Can you provide example code for a solution? Since this is a general
> Problem, maybe it would be helpful to add it
Hi Ernesto Reinaldo Barreiro ,
Can you provide example code for a solution? Since this is a general
Problem, maybe it would be helpful to add it to the wicket core libaries.
Have a happy new year,
Johannes Renoth
On 2019-12-30 16:52, Ernesto Reinaldo Barreiro wrote:
> Hi,
>
> One thing I immedi
Hi,
One thing I immediately do for any wicket application is rolling a blocker
DIV preventing users to double click on AJAX links: Situation? User clicks
in some AJAX link and meanwhile request is being processed the user clicks
on something "that will not be there" when AJAX request finishes. Thi
Hi!
We see these typos of errors every now and then too. It’s usually people
navigating to old pages, double clicking on links etc.
Nevertheless, in our logs these are relatively easy to find: we send out
e-mail notifications when such errors occur, and the e-mail includes quite
some details (pag
In our experience these can be a mixed bag of expired requests, expired
links, incorrect back button presses (and links from stale pages), session
timeouts, etc.
We haven't been able to trace them either, if a solution exists, I wish it
was part of wicket core.
Using more human readable urls migh
Hello,
We have pretty widely used software with thousands of visits per day.
And from time to time we observe pretty weird Wicket related errors
in logs. Commonly it's something about components structure: no such
child, there is already such element and etc. But the problem is that
commonly we c