This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29204 - Not sure what it means to emulate the sendKeys natively
Summary: Not sure what it means to emulate the sendKeys natively
Status: RESOLVED FIXED
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20860
  Show dependency treegraph
 
Reported: 2015-10-15 15:36 UTC by John Jansen
Modified: 2016-01-11 11:21 UTC (History)
3 users (show)

See Also:


Attachments

Description John Jansen 2015-10-15 15:36:34 UTC
"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?
Comment 1 Andreas Tolfsen 2015-10-15 15:47:46 UTC
Do note that this chapter hasn’t been redefined.  There’s a big warning at the top.
Comment 2 Simon Stewart 2016-01-11 11:21:50 UTC
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.