29204 2015-10-15 15:36:34 +0000 Not sure what it means to emulate the sendKeys natively 2016-01-11 11:21:50 +0000 1 1 1 Unclassified Browser Test/Tools WG WebDriver unspecified PC Windows NT RESOLVED FIXED P2 normal --- 20860 1 johnjan public-browser-tools-testing ato mike simon.m.stewart public-browser-tools-testing oldest_to_newest 123718 0 johnjan 2015-10-15 15:36:34 +0000 "When the user input is emulated natively " Two issues: 1. I'm not sure what the intention of "natively" is here. How else would one emulate the keyboard? Why is there a difference between "native" emulation and otherwise? 2. The next statement is "see note below" but I do not see a note anywhere. Maybe that is meant to answer my question above? 123719 1 ato 2015-10-15 15:47:46 +0000 Do note that this chapter hasn’t been redefined. There’s a big warning at the top. 124558 2 simon.m.stewart 2016-01-11 11:21:50 +0000 The Element Send Keys section doesn't contain this text any more. In answer to the main question, on Windows there are at least four options for emulating user input to the browser. You could use the Win32 SendInput API, pump events directly into the browser's message queue, creating the events in the browser itself, or (least effectively, and not within spec) emulating the user input via JS.