Excellent, this is just what I was looking for.

Thanks again for the help
manu

On 1/4/2011 6:03 PM, Jari Bakken wrote:
This is documented on the WebDriver wiki:

http://code.google.com/p/selenium/wiki/RubyBindings

Basically, you want to do something like this:

   client = Selenium::WebDriver::Remote::Http::Default.new
   client.timeout = 120 # seconds - default is 60
   driver = Selenium::WebDriver.for(:firefox, :http_client =>  client)

   browser = Watir::Browser.new(driver)

On Tue, Jan 4, 2011 at 11:59 PM, Emmanuel Cecchet<[email protected]>  wrote:
Hi all,

I was finally able to catch the stack trace of the timeout (see below). Even
when the error occurs, the operation continues and the keystrokes are still
sent to the browser.
I am not sure how to override the read timeout in protocol.rb, any
suggestion?

Timeout::Error: execution expired
        from C:/Ruby187/lib/ruby/1.8/timeout.rb:64:in `rbuf_fill'
        from C:/Ruby187/lib/ruby/1.8/net/protocol.rb:134:in `rbuf_fill'
        from C:/Ruby187/lib/ruby/1.8/net/protocol.rb:116:in `readuntil'
        from C:/Ruby187/lib/ruby/1.8/net/protocol.rb:126:in `readline'
        from C:/Ruby187/lib/ruby/1.8/net/http.rb:2028:in `read_status_line'
        from C:/Ruby187/lib/ruby/1.8/net/http.rb:2017:in `read_new'
        from C:/Ruby187/lib/ruby/1.8/net/http.rb:1051:in `request'
        from C:/Ruby187/lib/ruby/1.8/net/http.rb:1037:in `request'
        from C:/Ruby187/lib/ruby/1.8/net/http.rb:543:in `start'
        from C:/Ruby187/lib/ruby/1.8/net/http.rb:1035:in `request'
        from
C:/Ruby187/lib/ruby/gems/1.8/gems/selenium-webdriver-0.1.2/lib/selenium/webdriver/remote/http/default.rb:36:in
`request'
        from
C:/Ruby187/lib/ruby/gems/1.8/gems/selenium-webdriver-0.1.2/lib/selenium/webdriver/remote/http/common.rb:36:in
`call'
        from
C:/Ruby187/lib/ruby/gems/1.8/gems/selenium-webdriver-0.1.2/lib/selenium/webdriver/remote/bridge.rb:429:in
`raw_execute'
        from
C:/Ruby187/lib/ruby/gems/1.8/gems/selenium-webdriver-0.1.2/lib/selenium/webdriver/remote/bridge.rb:407:in
`execute'
        from
C:/Ruby187/lib/ruby/gems/1.8/gems/selenium-webdriver-0.1.2/lib/selenium/webdriver/remote/bridge.rb:324:in
`sendKeysToElement'
        from
C:/Ruby187/lib/ruby/gems/1.8/gems/selenium-webdriver-0.1.2/lib/selenium/webdriver/common/element.rb:123:in
`send_keys'
        from
C:/Ruby187/lib/ruby/gems/1.8/gems/selenium-webdriver-0.1.2/lib/selenium/webdriver/common/element.rb:114:in
`each'
        from
C:/Ruby187/lib/ruby/gems/1.8/gems/selenium-webdriver-0.1.2/lib/selenium/webdriver/common/element.rb:114:in
`send_keys'
        from
C:/Ruby187/lib/ruby/gems/1.8/gems/watir-webdriver-0.1.8/lib/watir-webdriver/elements/text_field.rb:17:in
`set'
        from (irb):17

Thanks
manu

On 1/4/2011 3:45 PM, manu wrote:
Hi all,

I am writing a pretty big chunk of text in a form and want to keep the
default typing speed in the form to emulate a real user.
So when I call:
browser.text_field(:name, 'field').set('some very long text here')

The operation stops before completion with a timeout.
Is there a way I can override the timeout in the set operation so that
it can complete?
Any other workaround you can suggest?

Thanks
manu

--
Before posting, please read http://watir.com/support. In short: search
before you ask, be nice.

[email protected]
http://groups.google.com/group/watir-general
[email protected]


--
Before posting, please read http://watir.com/support. In short: search before 
you ask, be nice.

[email protected]
http://groups.google.com/group/watir-general
[email protected]

Reply via email to