Note that there are some explanatory texts on larger screens.

plurals
  1. POSelenium Server on CentOS 6.2 has no keyboard input while testing
    primarykey
    data
    text
    <p>We currently have a problem with <strong>SeleniumServer</strong> which is troubling me for 2 days, now...hope you can help me.</p> <p><strong>The Selenium Server</strong> is running on a <strong>CentOS 6.2</strong>, <strong>Selenium Server is 2.21</strong> and <strong>Firefox is 10.0.4</strong>. </p> <p>When a test is starting up, <strong>SeleniumServer</strong> launches <strong>Firefox</strong> but he can not type anything in the form fields or press "Enter" to submit. </p> <p>Even better, no one (not even me with <strong>VNC-Server</strong>) can write something in the form field, url bar, menus, press a key like "Enter", etc....it is as the keyboard is not present... It´s like <strong>Firefox</strong> is locked somehow.</p> <p>If a start <strong>Firefox</strong> with <strong>Interactive-Mode</strong> : <code>selenium-server.jar -interactive</code> &amp; <code>cmd=getNewBrowserSession&amp;1=*firefox&amp;2=http://www.google.com</code> everything is working fine, I can do all the tests manually. </p> <p>I can also start firefox manually with just typing <code>firefox</code> in the shell and that is working fine, too.</p> <p>So what is going on in <strong>Selenium</strong> and how does <strong>Selenium</strong> starts <strong>Firefox</strong>? Why is no <strong>Keyboard-Input</strong> available when running a <strong>Selenium-Test</strong> with <strong>SeleniumServer</strong>? We tested with <strong>MacOS</strong> and <strong>Windows</strong>, too and both working fine with the same test.</p> <p>Any idea would be appreciated.</p> <p>Greetings from Berlin</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload