Official Selenium Blog

August 2, 2011

Selenium 2.3 Released

Filed under: Releases — shs96c @ 12:34 pm GMT+0000

Continuing our new tradition of weekly releases, we’re very pleased to announce the release of Selenium 2.3. The release notes for this version are pretty slim:

  • Better detection of clickable areas in Firefox.
  • Merge of Google-contributed code into the underlying javascript libraries used by the drivers.
We’ve also fixed bugs, one of which was being a nuisance for users of IBM’s JRE. The complete changelog can be found in the zipped downloads or in our source tree.
If you’re a Chrome user, then it’s a great idea to head over to the Chromium project’s download page to pick up the executable used by the ChromeDriver. It’s recently been updated, and now includes support for handling alerts and prompts! Thanks, Google!


  1. Great job on the frequent releases. Given that the versioning schema is major.minor.revision, I was expecting that the revision number will be updated for the weekly releases instead of the minor number. At the current pace Selenium 3 will be released in 7 weeks. The minor number is usually updated when some new functionality has been added.

    Can you explain the versioning scheme for the project? Should we expect to the the revision number change?

    Comment by Quantum Mechanics — August 2, 2011 @ 1:04 pm GMT+0000 | Reply

    • In the x.y.z version that is being used, the x.y is the project version and the .z can be used by intermediate releases by the individual language bindings. So lets say that the Ruby one needed an extra lease then there could be a 2.3.1 of the gem, but only be a 2.3.0 of the Python egg.

      (Or at least that is how I understand it.)

      Comment by adam goucher — August 3, 2011 @ 8:39 pm GMT+0000 | Reply

  2. What version of Chrome does this release support Alerts on?

    org.openqa.selenium.WebDriverException: Alerts are not supported for this version of Chrome (WARNING: The server did not provide any stacktrace information)
    Build info: version: ‘2.3.0’, revision: ‘13158’, time: ‘2011-08-01 18:14:01’
    System info: ‘Windows XP’, os.arch: ‘x86’, os.version: ‘5.1’, java.version: ‘1.6.0_26’

    Comment by bdk — August 2, 2011 @ 11:08 pm GMT+0000 | Reply

    • You need the latest version of Chrome in order for this to work.

      Comment by shs96c — August 7, 2011 @ 8:44 pm GMT+0000 | Reply

  3. The version on Maven central doesn’t work since central doesn’t have version 3.3.0.

    Comment by vmassol — August 4, 2011 @ 4:40 pm GMT+0000 | Reply

    • 2.3.1 has been released to address this.

      Comment by shs96c — August 7, 2011 @ 8:43 pm GMT+0000 | Reply

  4. Am I the only one, or is the realitive url logic flaky in the web driver model? Even with the basepage set, my code still bombs out on the second page trying to go to “www.login.aspx” instead. It never seemed to happen with RC. I have a workaround in place for now, but I’d love to know if anybody else has experienced this

    Comment by Jonathan — August 5, 2011 @ 8:25 am GMT+0000 | Reply

  5. Does 2.x include flow control or is an extension required? If so, where is the best one?

    Comment by John Ekstedt — August 5, 2011 @ 6:18 pm GMT+0000 | Reply

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Create a free website or blog at

%d bloggers like this: