Closed lukeis closed 8 years ago
This problem is still exposed in Selenium 2.7.
Reported by gaphor
on 2011-10-06 18:57:28
The commit leading to this problem is:
SimonStewart: There seems to be an odd problem when emulating 'type' into a rich
text area.
Falling back to using sendKeys directly
https://selenium.googlecode.com/svn/trunk@12156
This patch adds an extra clear() command to ensure the text area is cleared before
text is added.
Reported by gaphor
on 2011-10-06 20:37:35
Calling clear before sendKeys may have side effects when you have blur/focus handlers.
I don't think that this is a good general solution.
In our case, sending Ctrl+A / Cmd+A to select the field's content before the "real"
sendKeys worked reliably.
Reported by mguillemot@yahoo.fr
on 2011-10-07 06:22:04
Main issue is that the current selenium emulation is inconsistent with the behavior
in Selenium IDE.
I suppose sending a ctrl-A / cmd-A can solve this just as well, although I'm not sure
how that can be achieved.
Are those events fired by the native browser (e.i. out of control of selenium?)
Reported by gaphor
on 2011-10-07 07:44:11
Reported by barancev
on 2011-10-13 06:01:32
The WebDriverBackedSelenium is provided as a tool for allowing teams to migrate from
RC to WebDriver, not as a perfect replacement (though we do try and be correct). I've
put in a temporary fix that may work, but the best advice would be to do something
like:
WebDriver driver = ((WrapsDriver) selenium).getWrappedDriver();
WebElement element = driver.findElement(By.id("foo"));
element.clear();
element.sendKeys("Your text here");
Reported by simon.m.stewart
on 2012-02-20 22:11:55
This issue was closed by revision r15931.
Reported by simon.m.stewart
on 2012-02-20 22:12:47
Fixed
Reported by luke.semerau
on 2015-09-17 18:13:10
Originally reported on Google Code with ID 1982
Reported by
gaphor
on 2011-07-04 17:09:50