Hey Ralf,
I finally worked this out !
It's a caching issue. Jetty is not getting the XMLHttpRequest cos IE
is using the response from the cache and getting the old command
(until the next second ticks over :-)
So.. to fix it add these lines to SeleneseJettyResourceHandler.handle() :
res.setField(HttpFields.__ContentType, "text/plain");
res.setField(HttpFields.__CacheControl, "no-cache");
res.setField(HttpFields.__Pragma, "no-cache");
res.setField(HttpFields.__Expires, "-1");
Please let me know if this works for you, and I'll commit the change.
Cheers,
Darren.
>
Hello,
when executing a series of Selenium commands against
the Internet
Explorer, each command is executed multiple times. Commands
are
sometimes executed in the wrong order. Does anyone
have an
idea how this can happen or experienced something
similar?
The setup:
- Driven Mode using the Java Driver (please continue
to read anyway ;)
- Internet Explorer 6.0
- Windows XP
I understand that there may be racing conditions when
the browser-bot
communicates with the Java Driver. This may cause the
command order
problems. But I don't understand yet why commands are
being fired up to
80 times in a row.
I checked what commands the Java driver sends to the
browser-bot. The
Java driver places each command exactly once in the
SingleEntryAsyncQueue using
SingleEntryAsyncQueue.put(). So the driver
side seems to be fine. What could go wrong whith the
browser-bots
working off of the queue?
Cheers for a hint,
Ralf
_______________________________________________Selenium-devel mailing
[EMAIL
PROTECTED]://lists.public.thoughtworks.org/mailman/listinfo/selenium-devel
_______________________________________________
Selenium-devel mailing list
Selenium-devel@lists.public.thoughtworks.org
http://lists.public.thoughtworks.org/mailman/listinfo/selenium-devel
