It's fixed now. Someone has checked into version control html with
wicket:header section. That section sent to browser incompatible javascript
that caused wicket to fail.
Thanks,
Dave
On Wed, Oct 5, 2011 at 4:23 PM, Dawid Dudzinski wrote:
> Hello,
>
> I need a help understanding an error I'm re
Hello,
I need a help understanding an error I'm receiving.
We have a screen divided into 2 pieces. Left side acts almost independently
from the right. Everything works until a call is made and entire right side
swapped out for another content (A call to .replace(Component) is made).
Expected beha