jeffery Reporter
	Description • 6 years ago

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180316021353

Steps to reproduce:

Firefox 59.0.1 (64-bit)
selenium-webdriver 3.11.0
geckodriver 0.20.0
Ubuntu 17.10 (64 bit)

Code (navigate.rb):

require 'selenium-webdriver'

driver = new Selenium::WebDriver.for :firefox  # error here line 3
driver.navigate.to 'http://google.com'
driver.quit





Actual results:

Uncaught exception: undefined method `new' for main:Object
	/home/jeffery/RubymineProjects/selenium/navigate.rb:3:in `<top (required)>'

Using RubyMine, it looks like the for method gets to its last step in driver.rb:

def initialize(bridge, listener: nil)
        @bridge = bridge
        @bridge = Support::EventFiringBridge.new(bridge, listener) if listener
end

The error occurs upon return from this  superclass constructor, which should return back through the stack to the original for method.  Everything to this point appears to be set up properly: geckodriver is started, the session request is successful, and  browser window appears.  It seems like the ruby stack is corrupted in some fashion.


Expected results:

A functional driver instance.

	jeffery Reporter
	Comment 1 • 6 years ago

Also:  Ruby 2.5.0

	Henrik Skupin [:whimboo][⌚️UTC+1]
	Comment 2 • 6 years ago

This is not a bug tracker for the Ruby Selenium binding. You want to ask over there for support. Thanks.

	Andreas Tolfsen ❲:ato❳
	Comment 3 • 6 years ago

The right bug tracker is https://github.com/seleniumhq/selenium/issues.