And thanks again for feedback and comments! On Thu, Apr 18, 2019 at 10:24 AM Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote:
> Hi, > > Just to follow up. This was neither a wicket error nor a chrome problem > but some weird combination of non rolled back transaction + some > transaction controlling filter on top of of wicket filter (that was somehow > truncating response). > > On Tue, Apr 16, 2019 at 6:36 PM Maxim Solodovnik <solomax...@gmail.com> > wrote: > >> Maybe non-minimized stacktrace can gave some more info? >> >> On Tue, 16 Apr 2019 at 22:35, Ernesto Reinaldo Barreiro >> <reier...@gmail.com> wrote: >> > >> > Hi, >> > >> > Bumping jQuery version to 3.4.0 provides same results (no minimized). >> > >> > On Tue, Apr 16, 2019 at 5:28 PM Maxim Solodovnik <solomax...@gmail.com> >> > wrote: >> > >> > > non minified jquery and/or wicket.mode=DEVELOPMENT >> > > May be it will shed some light on this issue ... >> > > >> > > On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro < >> > > reier...@gmail.com> >> > > wrote: >> > > >> > > > Hi, >> > > > >> > > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik < >> solomax...@gmail.com> >> > > > wrote: >> > > > >> > > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? >> > > > > >> > > > >> > > > Do you mean jquery non minified jQuery? >> > > > >> > > > -- >> > > > Regards - Ernesto Reinaldo Barreiro >> > > > >> > > >> > > >> > > -- >> > > WBR >> > > Maxim aka solomax >> > > >> > >> > >> > -- >> > Regards - Ernesto Reinaldo Barreiro >> >> >> >> -- >> WBR >> Maxim aka solomax >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > -- > Regards - Ernesto Reinaldo Barreiro > -- Regards - Ernesto Reinaldo Barreiro
