Selenium version: 1.8.0
os: windows 7 64bit
browser: firefox v. 12.

In previous version of selenium 1.7.2 and firefox version 11. it was working like:
fill in this field.
In versions mention in the beginning of my comment when command: typeKeys is executed
there is no action like this comment was not execute. 

command type is working fine, but for typeKeys nothing happens. 

The reason for this is that the mechanism used for updating keyboard events changed
between Firefox 11 and 12 (r16768) We need to apply a similar fix to Core.

If we weren't maintaining old functionality, I'd replace the entire code path with
the atoms, which would ensure that this sort of thing never happened again. But we
are, so I won't.

Issue 3798 has been merged into this issue.

Issue 3801 has been merged into this issue.

Hi,

As Simon pointed out, the Selenium Core component that is being used by Selenium IDE
is being put on the back burner. The mechanism that was used for keyboard no longer
works on Firefox 12. I will try to find a way of using the new atoms from Selenium
IDE for the keyboard events. In the meanwhile, try to use type instead of typeKeys.
Unless your application code depends on getting the key* events fired, it should work.

If you have seen the videos from Selenium Conference 2012, Webdriver based playback
will be available in Selenium IDE soon. I am working on the final few enhancements
but it should make it out soon. Using WebDriver based playback, typeKeys should start
working again.

Cheers,
Samit

Howdy,

Any guesstimate when will a fix for this bug will be released (Webdriver based playback
)? 

I was using the typeKeys function in a drop-down selection-kind-of-thingie where the
type function simply does not work.


Cheers,
Juha

This is my HTML code How to write TypeKeys. Can any one explain to me 


<input id="ext-comp-1031" class=" x-form-text x-form-field x-form-empty-field" type="text"
name="ext-comp-1031" autocomplete="off" size="20" style="width: 260px;">

Hello, 

I too would like to know an estimated time on repair of the TypeKeys function; we rely
heavily on this command for much of our application testing.

Thanks, 

Mike 

I just ran into this issue myself after upgrading to Firefox 12 on my selenium server
and I found a workaround...

type | locator |string
typeKeys | locator | string

Great workaround.

Thanks

How is this a work around? This just looks like the standard syntax for the type and
typeKeys commands.

Since upgrading to Firefox 12, 13, and now 14 which was released yesterday, type and
typeKeys has been rendered useless.

I hope there is a definite fix work around on the horizon.

Introduced new command sendKeys r17511.

Hi, thanks for the update. 

I have a question though. How can one send special characters using the sendKeys command?
For example I went to press ENTER, how do I do that?

Hello,

I posted my comments almost 3 months ago ... No reply since then ... Can anyone throw
some light on my question?

If found a work around. Take a look at this guy's page:
https://coderwall.com/p/n2kasa

In my case, I couldn't add more javascript to the web site itself, but if you take
all the comments out of this guy's example code, you can put the javascript in a runScript
command in the IDE.

Guys, I am using selenium RC, where typeKeys become useless too. are you planning to
add sendKeys to RC ?

Hi Guys i have verified with the latest firefox version 17.0.1 and with selenium 2.28.0
server jar file ,the typekeys command is not yet working , can any one update me a
solution on this.

The workaround I mentioned in in Comment 16 definitely works with the latest version
of Firefox and Selenium. Short of fixing Selenium yourself, that's probably your best
bet.

or just use keyDownNative() etc. for selenium rc - I found only native methods still
work

http://blog.reallysimplethoughts.com/2012/07/19/new-selenese-command-sendkeys/

The new command seems it would take a lot of re-writing of tests not just replacing
the typeKeys but also adding other code to change the text on the page so it'll be
kind of pain for people that have a lot of tests that worked previously with the typeKeys.
Is there a work around to make the typeKeys command work in the same way again?

Using FireFox 18.0.2, Selenium-Server-2.29.0 typeKeys(locator,value) and type(locator,value)
do not function at all. Even the suggested combination of using both 

selenium.type(locator,value)
selenium.typeKeys(locator,value)

The Selenium 2 Webdriver sendKeys(locator,value), works perfectly, however mix matching
server and webdriver does not produce the desired results. Having type and typekeys
function properly is critical to the companies automation framework. 
Anyone have a work around...?  

I tested typeKeys with selenium ide 2.1.0.. and supprissingly this issue is not yet
fixed.any updates when this will be fixed. 

As in my project the result matching the searched criteria will be simulated on keytype
event. (as in your enter something and it will start searching like.. we do in google.com)

Hi,

The typeKeys command is broken beyond repair, hence the sendKeys command was introduced.
Please try to use it instead. If you are worried about changing tons of tests, try
using my Selenium Expert plugin. It can reduce the changes required significantly.

I have not tried it, but typeKeys might work if you use WebDriver playback in Selenium
IDE v2.1.0.

Cheers,
Samit Badle
Selenium IDE Maintainer
@samitbadle
http://blog.reallysimplethoughts.com/

Hi,

Just a heads up, typeKeys and other *Key* command will be deprecated soon. Consider
using sendKeys instead.

Cheers,
Samit Badle
Selenium IDE Maintainer
@samitbadle
http://blog.reallysimplethoughts.com/

Hi Samit,

If sendKeys will be the new command for this, will there ever be Selenium RC/Selenium
Server support for this command? It would likely break many test frameworks if this
command is deprecated without sendKeys being a valid substitute for implementations
using RC/Server.

Thanks,
George

I am getting the following error in one of my scripts when I call the sendKeys command
(which I moved to from using various "type" commands at Samit's request). Note that
I need the keyups from sendKeys to validate the form validation so I really need this
to work.:

[error] Unexpected Exception: code -> 11, message -> Element is not currently visible
and may not be manipulated, name -> ElementNotVisibleError, stack -> bot.Error@chrome://selenium-ide/content/selenium-core/scripts/atoms.js:3887
bot.action.checkShown_@chrome://selenium-ide/content/selenium-core/scripts/atoms.js:6945
bot.action.type@chrome://selenium-ide/content/selenium-core/scripts/atoms.js:6977 @chrome://selenium-ide/content/selenium-api-override.js:27
retval@chrome://selenium-ide/content/selenium-core/scripts/htmlutils.js:60 ActionHandler.prototype.execute@chrome://selenium-ide/content/selenium-core/scripts/selenium-commandhandlers.js:310
TestLoop.prototype._executeCurrentCommand@chrome://selenium-ide/content/selenium-core/scripts/selenium-executionloop.js:112
TestLoop.prototype.resume@chrome://selenium-ide/content/selenium-core/scripts/selenium-executionloop.js:78
retval@chrome://selenium-ide/content/selenium-core/scripts/htmlutils.js:60 , constructor
-> function (a, b) { this.code = a; this.message = b || ""; this.name = bot.Error.NAMES_[a]
|| bot.Error.NAMES_[bot.ErrorCode.UNKNOWN_ERROR]; var c = Error(this.message); c.name
= this.name; this.stack = c.stack || "" }, isAutomationError -> true, toString -> function
() { return this.name + ": " + this.message }, fileName -> , lineNumber -> 0, columnNumber
-> 0

It is happening in FF22 with Selenium IDE 2.1.0 as well as after I moved back to the
previous version of firefox with the previous version of IDE.

WHat is strange is that I use sendKeys successfully throughout the test and, after
a clickandwait command on a link, it fails.

Even MORE strange is that when I issue the commands individually by double clicking
in IDE, they work (just not when I run the test.

@asmodaie:

I am not sure if Selenium RC would ever get it as Selenium RC is end of life. If you
are still dependent on Selenium RC, you should start planning to migrate away from
it. Watch the excellent keynote at Selenium Conference 2013 from Jason at http://www.youtube.com/watch?v=cSLmfegT36A

If you start using webdriver, it solves the problem completely as sendKeys is supported
by WebDriver. If you are not using WebDriver, at least start using WebDriver backed
Selenium and then you can use the sendKeys command directly on the WebDriver instance
that is being used. So test frameworks should start preparing for this.

Cheers,
Samit Badle
Selenium IDE Maintainer
@samitbadle
http://blog.reallysimplethoughts.com/

@peter.gibbons@canvaspop.com: Sometimes Selenium is just too fast :) Try adding a waitForElementPresent
just before the sendKeys and see if it helps. The reason for this is that the page
has loaded, but the element is not yet displayed. I am happy to hear that you are using
sendKeys successfully throughout your test. I hope more users would switch to it.

Cheers,
Samit Badle
Selenium IDE Maintainer
@samitbadle
http://blog.reallysimplethoughts.com/

Hi,

i dont find selenium.sendKeys() in Selenium class. I have tried using selenium-java
versions till 2.9. Kindly help me on this.

Thanks and Regards,
Arun

Issue 3926 has been merged into this issue.

Tendando'm using Sendkey, it is not a recognized Selenium Server (formerly the Selenium
RC Server) command.

Any solution?

Selenium RC is deprecated and the support of Selenium RC is discontinued.

Selenium team is not going to fix remaining issues in Selenium RC and we don't accept
new issue reports on Selenium RC.

On the other side, we continue to accept pull requests and patches from the community.