Hi all, I spend a considerable amount of time on getting our changes for window.onerror launched in open source: https://gwt-review.googlesource.com/#/c/gwt/+/18880/
This causes some tests to fail in html unit: http://build.gwtproject.org/job/gwt/972/testReport/ Note: these tests are already failing but not reported failing with the newer version of HTML unit. As soon as we are starting to trap window.onerror in tests we actually catch the exception and thus fail those 6 test cases. Things I have tried: - Place @DoNotRun on the tests, does not work for the JUnit tests since they require all methods to run - Downgrade HtmlUnit in open source, fails with a noclass def for WebSocket out of Jetty - Upgrade HmltUnit to latest (2.27), fails to start the testing shell in open source Trapping window.onerror the default in open source GWT is important and the right way forward, we simply do not have the bandwith to do it right now. A simple way of making it happen would be to roll back the jetty upgrade. We are not going to invest further into this for OS, but would rather see somebody else pick this up. Any takers? -Daniel -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujir8N8Bs4MKsGeeVpd3uqT5JxQbduUDNEiVZN6zm2zVT2A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
