We're trying to use Selenium 2.0b3 to verify behavior of a Java web site we've recently acquired from a third party. The site often uses AJAX to plop HTML replacements onto the page.
Internet Explorer, however, findElement of any form input followed by sendKeys only works half the time. For the findElement, we're using a WebDriverWait with an ExpectedCondition returning the element we want, and that returns successfully. Observing the results of the sendKeys on this element, though, we often see nothing appear in the field.
We have no problems filling out login forms that are initially loaded when the HTML page initially loads; these problems seem to entirely occur on anything that's just been loaded with an innerHTML change through an asynchronous request. (We also, perhaps unsurprisingly, don't have these problems with Firefox.)
Adding arbitrary time delays after the page transition but before doing the findElement doesn't appear to help. (I tried waiting for 10 seconds after we saw the async request finish setting innerHTML and the problem still occurred occasionally.)
Any idea what this might be, or how to work around it?
EDIT: Just to be clear, this is happening under IE with Selenium 2 WebDriver.