Fixed it with a horrid hack, for now: http://gist.github.com/294620 <http://gist.github.com/294620>I've found a few places in Capybara where I've had to drop to underlying framework code, or even Nokogiri, to get and set values. Still, it runs with webdriver a treat! Cheers, Doug.
On 4 February 2010 14:29, Caius Durling <[email protected]> wrote: > On 4 Feb 2010, at 14:13, Francis Fish wrote: > > Top of me head no idea, personally I would do something like: > > x = find( "//*...@class = 'current']//input" ) > > > > > > and then print x out. It looks like you're searching for the same thing > > > > x.set(value) > > > > puts x.inspect > > > > y = find ... > > > > puts y.inspect > > > Personally I'd drop into the debugger just before that (require > "ruby-debug"; debugger) and inspect what it's doing whilst it runs. Off the > top of my head no idea, possibly a race condition where it hasn't updated > the value, or set() sets a different attribute than value() returns. Poke it > a bit and I'm sure you'll find the answer :) > > C > --- > Caius Durling > [email protected] > +44 (0) 7960 268 100 > http://caius.name/ > > -- > You received this message because you are subscribed to the Google Groups > "NWRUG" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nwrug-members%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nwrug-members?hl=en. > > -- You received this message because you are subscribed to the Google Groups "NWRUG" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nwrug-members?hl=en.
