Private method 'select' called for Selenium::WebDriver::Element #458

Closed
mus0u opened this Issue Aug 18, 2011 · 3 comments

Comments

Projects
None yet
4 participants
@mus0u

mus0u commented Aug 18, 2011

Running the given step with Cucumber causes this error to occur. It's extremely puzzling, and I've tried three different versions of Firefox, and additionally tried Chrome, all to no avail in solving it.

Private method 'select' called for #<Selenium::WebDriver::Element:0x1112c1e80> (NoMethodError) ./features/step_definitions/web_steps.rb:73 ./features/step_definitions/web_steps.rb:14:in 'with_scope' ./features/step_definitions/web_steps.rb:72:in '/^(?:|I )select "([^"]*)" from "([^"]*)"(?: within "([^"]*)")?$/'

@weidenfreak

This comment has been minimized.

Show comment
Hide comment
@weidenfreak

weidenfreak Aug 19, 2011

Is it possible that you are using a new selenium-webdriver (> 2.0) with an old capybara version (1.0.0)?

I was playing around with different versions of capybara and selenium-webdriver to find out why Capybara 1.0.1 is buggy in some projects and got this error as well.

You shouldn't get this error if you don't change the dependencies. If you didn't change any dependency you could try running 'bundle update capybara'.

Is it possible that you are using a new selenium-webdriver (> 2.0) with an old capybara version (1.0.0)?

I was playing around with different versions of capybara and selenium-webdriver to find out why Capybara 1.0.1 is buggy in some projects and got this error as well.

You shouldn't get this error if you don't change the dependencies. If you didn't change any dependency you could try running 'bundle update capybara'.

@joliss

This comment has been minimized.

Show comment
Hide comment
@joliss

joliss Aug 19, 2011

Collaborator

I think Meike might be right about that. If that doesn't help, I would recommend you try the Capybara mailing list for help with getting it running. We try to only have reproducible issues on this issue tracker.

Collaborator

joliss commented Aug 19, 2011

I think Meike might be right about that. If that doesn't help, I would recommend you try the Capybara mailing list for help with getting it running. We try to only have reproducible issues on this issue tracker.

@joliss joliss closed this Aug 19, 2011

@jasonm

This comment has been minimized.

Show comment
Hide comment
@jasonm

jasonm Oct 26, 2011

FWIW I can confirm I saw this when I had selenium-webdriver 2.9.1 and capybara 0.4.1.2, which is obviously a bad idea ;)

jasonm commented Oct 26, 2011

FWIW I can confirm I saw this when I had selenium-webdriver 2.9.1 and capybara 0.4.1.2, which is obviously a bad idea ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment