Hi, >> do you use the latest WebTest build containing HtmlUnit-2.5? > Well, I am using Webtest 3.0 and not the latest (development) build, > but I think that would qualify as a yes.
no, this is a no: WebTest 3.0 uses HtmlUnit-2.4 >> If clicking a button doesn't produce the same behavior as in the simulated >> browser, >> then it is a bug in HtmlUnit. In this case, opening an issue with the >> smallest possible example allowing to reproduce the problem is the best >> thing to do. As workaround, you can try to simulated other browser version. >> > Well, as far as I understand the problem, it's a conflict between the > design of SmartClient and some common assumptions made when dealing > with web applications. (Switching browsers does not fix anything; the > problem is in how SmartClient applications register events via an > eventproxy buried somewhere in their internal JavaScript code, and > how, instead of relying on the browser's "click" event, they rely on > the lower-level mouseDown/mouseUp.) I will do that, when I have the > time, but I fear that the changes necessary to accomodate SmartClient > would be a little too important, and that something like a plugin > would be a better solution. if this is something that works in a "normal" browser without extra plugin, then it should work in HtmlUnit. If it doesn't, then it is a bug of HtmlUnit. Cheers, Marc. -- Web: http://www.efficient-webtesting.com Blog: http://mguillem.wordpress.com _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
