Brian Tomlin wrote:
> Daniel, I think you and I are leading parallel lives. I saw the same 
> thing in a script I had that was something like this:
> 
> require 'rubygems'
> require 'watir'
> 
> ie = IE.new
> 
> 
> It used to work, but for some reason to get it to work now I had to 
> change the last line to:
> 
> ie = Watir::IE.new
> 
> 
> I hope this works for you.

I've always used Watir::IE.start(string).

Currently, this is working, but calling...

browser = Watir::IE.start(uri)
browser.text_field(:id, text_field_id)

Is raising:

uninitialized constant 
Watir::InputElementLocator::MissingWayOfFindingObject Exception

Did they change the API and not tell anyone? As far as I can tell via 
the cheatsheet (http://secretgeek.net/watir_cheatsheet.asp) they 
haven't. What gives?
-- 
Posted via http://www.ruby-forum.com/.