Re: [gwt-contrib] Re: Jetty upgrade broke HtmlUnit for window.onerror

2017-10-10 Thread 'Goktug Gokdogan' via GWT Contributors
tbroyer: Are you using batch mode while testing? We are using -batch module internally and maybe you guys do not externally? (though you linked the code that only runs in batch mode, IIRC). On Tue, Oct 10, 2017 at 1:04 PM, Thomas Broyer wrote: > I'll try with the manual

Re: [gwt-contrib] Re: Jetty upgrade broke HtmlUnit for window.onerror

2017-10-10 Thread Thomas Broyer
I'll try with the manual runstyle, i.e. with a real browser, and see how it goes. Thanks for the feedback. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [gwt-contrib] Re: Jetty upgrade broke HtmlUnit for window.onerror

2017-10-10 Thread 'Daniel Kurka' via GWT Contributors
I am not aware of anything specific we have done within Google, we never imported the jetty upgrade. I think you just go ahead for open source and make it work there. We do not care that much for htmlunit anymore within Google. On Tue, Oct 10, 2017 at 10:28 AM Thomas Broyer

Re: [gwt-contrib] Re: Jetty upgrade broke HtmlUnit for window.onerror

2017-10-10 Thread Thomas Broyer
On Tuesday, October 10, 2017 at 6:08:05 PM UTC+2, Colin Alworth wrote: > > Patch is accepted and merged into upstream HtmlUnit, see > https://sourceforge.net/p/htmlunit/bugs/1924/ for more detail. > > Daniel, when you can take a look at Thomas's question, we can get this > change made to open

Re: [gwt-contrib] Re: Jetty upgrade broke HtmlUnit for window.onerror

2017-10-10 Thread Colin Alworth
Patch is accepted and merged into upstream HtmlUnit, see https://sourceforge.net/p/htmlunit/bugs/1924/ for more detail. Daniel, when you can take a look at Thomas's question, we can get this change made to open source GWT as you requested. -- You received this message because you are subscribed