Then you could try to debug it using browser developer tools (inspect element, debugger etc.).
Usually there is an issue like conflicting js or missing dependencies (throws exception on js), or something along those lines. Also could be that dependencies are injected in wrong order, or you might accidentally override some default js you are normally providing. I would maybe start by taking a diff between a browser page (source) without the change and a browser page (source) with the change, maybe it will point you to some direction. ** Martin ti 14. huhtik. 2020 klo 7.05 LSomefun (oyesomefunla...@gmail.com) kirjoitti: > No notification on console/browser log. > > -- > Sent from: > http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
