Thanks, I thought there might be a more appropriate forum.

But fortunately I won't have to post there - figured it out.

To find & verify the xpaths, I'd been using firebug.  Then looking in
the code I noted that firebug's model wasn't matching the actual HTML,
which in turn didn't match what nokogiri saw - they each showed
something different (bug elsewhere?).  Once I figured out what HTML
nokogiri was parsing, it was easy.

Thanks,
Alex

On Wed, 2010-08-18 at 15:49 -0500, Mike Dalessio wrote:
> Hi,
> 
> On Wed, Aug 18, 2010 at 3:58 PM, Alex Stahl <astahl / hi5.com> wrote:
> 
> > Hi Folks - Having some trouble w/ Nokogiri & its handling of xpaths and
> > nodesets, wondering if anyone here knows about possible existing issues.
> > (Apologies if this is a bit off-topic, but I am working in Ruby...)
> >
> 
> A better place to discuss Nokogiri-specific questions like this is probably
> the nokogiri-talk mailing list, which you can find more about here:
> 
>     http://groups.google.com/group/nokogiri-talk
> 
> 
> >
> > So I'm trying to access a form's action URL so that I can construct my
> > own query string to GET via mechanize.  I've tested just about every
> > possible xpath to get to the form's action property, and Nokogiri is
> > behaving as if it doesn't exist.
> >
> 
> When you email the nokogiri-talk list, please make sure you include the
> entire HTML document you're dealing with (e.g., as a gist or pastie), so
> that someone can first reproduce your issue and then diagnose it or give you
> some advice.
> 
> Cheers,
> -mike