[wtr-general] Re: Dealing with , and triggering Javascript

2009-07-08 Thread Dylan
I have version REXML 3.1.7.2 installed. I have managed to find a workaround now (Adding the font tag to watir) that probably works better than an xpath would, in fact, but from what I've seen very few people have gotten xpaths to work with watir (at least the element_by_xpath part) in the first p

[wtr-general] Re: Dealing with , and triggering Javascript

2009-07-08 Thread Željko Filipin
On Tue, Jul 7, 2009 at 7:52 PM, Dylan wrote: > I've even copied the exact html and ruby code given in the "What to do > for elements not having class in Watir?" section, and I still get nil > returned. I think you have to have newer version of rexml (3.1.6) than the one shipped with some versions

[wtr-general] Re: Dealing with , and triggering Javascript

2009-07-07 Thread Dylan
Thank you very much for the response, but unfortunately I am still having trouble. I tried browser.element_by_xpath("//fo...@title='Click Here']/") and I get "nil" returned. Predictably, when I try to call ".click" on that I get returned that click is an undefined method for nil:NilClass. I have t

[wtr-general] Re: Dealing with , and triggering Javascript

2009-07-07 Thread Dylan
Well, I finally figured out how to add to Watir, as you suggested, and that seems to work great. Thank you so much! -Dylan On Jul 3, 12:42 am, Željko Filipin wrote: > On Fri, Jul 3, 2009 at 12:54 AM, Dylan wrote: > > Click Here > > Try this: > browser.element_by_xpath("//fo...@title='Click He

[wtr-general] Re: Dealing with , and triggering Javascript

2009-07-03 Thread Željko Filipin
On Fri, Jul 3, 2009 at 12:54 AM, Dylan wrote: > Click Here Try this: browser.element_by_xpath("//fo...@title='Click Here']/").click More information: http://wiki.openqa.org/display/WTR/XPath And you can always extend Watir to make this possible: browser.font(:title, "Click Here").click http: