Okay, I'm about 80% sure that I understand and can remedy the problem within HtmlUnit itself. Will update once I finish syncing the apparently canonical SVN repo to git, so I can go over the history more carefully and ensure that this break isn't deliberate.
A question for my fellow GWT maintainers: should I patch the version of HtmlUnit that we presently use, so that we avoid breaking downstream expectations (plugins that specify specific browsers, use if IE8 or IE11 as a user agent to run the tests as)? Or should I see about getting this patch into the next version of HtmlUnit, and we wait on their release cycle, and leave this broken until then? -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/7647939e-7606-4697-84f7-da4f79f07aed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
