So currently we are only able to use Webdriver with Internet Explorer in
Quirks mode. With the Selenium 1 API, it was possible to use java key
events to open the developer toolbar and change the document mode.
Today, I've upgraded to Selenium 2.20 and I saw that they added the
possibility to use functions of the Selenium 1 API on a Webdriver
instance. Thus I tried to use my Selenium 1's trick to change the
document mode in Webdriver instance. That seems to work, but then an
assertion about a modal dialog is raised. That seems to be this issue:
http://code.google.com/p/selenium/issues/detail?id=3360
It was only fixed 2 days ago, so I'll have to wait the next release of
Selenium to try again (fortunately, it is released quite frequently).
But I'm getting a bit closer to the point when we will be able to
execute Webdriver instances of IE in all document modes (in particular
it will hopefully speed up the execution and maybe make IE9 mode usable).
--
Fr�d�ric Wang
maths-informatique-jeux.com/blog/frederic
I upgraded to Selenium 2.21 and indeed the bug I mentioned in my
previous message seems to be fixed now. So we can use Java keyboard
event to open the developer tool and select the document mode. That's
still not really perfect but that's probably the best solution until
they fix
http://code.google.com/p/selenium/issues/detail?id=2564
That means that we should now be able to use Webdriver with Internet
Explorer in all document modes. I hope that will speed up the execution
(compared to Selenium 1 API) and, for document IE9, avoid all these
timeouts that make it untestable. In particular, I hope we will finally
be able to test the SVG ouput in IE9 ;-)
As for other browsers, there is still the bug
http://code.google.com/p/chromium/issues/detail?id=89777#c4
preventing to take screenshots on Chrome linux with Webdriver.
I also saw that there is now a driver for Safari:
http://code.google.com/p/selenium/wiki/SafariDriver
but haven't tried yet.