search() returning fewer results with Mechanize than with Nokogiri about mechanize HOT 11 CLOSED

Can you please provide a test case that doesn't need network access? Or, if you'd like to discuss more, we can chat about this on the mailing list. Thanks.

from mechanize.

Hmm..I'm not sure how to do an offline version of this.

In line 12 of the gist above, I call get() to have the HTML loaded from a URL. Is there another way to load it, eg. from a string?

from mechanize.

Hmm..I'm not sure how to do an offline version of this.

In line 12 of the gist above, I call get() to have the HTML loaded from a URL. Is there another way to load it, eg. from a string?

from mechanize.

Hi! You can declare an inline xml doc like this:

xml = <<EOXML
<root>
  <some xml=true>foo</some>
</root>
EOXML

and then parse it with

Nokogiri::XML(xml)

from mechanize.

But I'm also hoping that you'll take the opportunity to try to narrow the problem down a bit, so that it's clear which <a> tags are found and which are not.

(In my above comment, replace XML with HTML as necessary).

from mechanize.

Sorry, but I don't really follow. Parsing a string with Nokogiri is not a problem, but I don't see how to do it with Mechanize?

The common pattern is:

agent = Mechanize.new

page = agent.get("http://google.com")

Instead of the second line above, how could I feed a string into the agent?

from mechanize.

You can do this via something like:

Mechanize::Page.new(nil, {'content-type'=>'text/html'}, your_html, 200, Mechanize.new)

from mechanize.

This appears to be a bug with Accept-Encoding: gzip, the downloaded file is too short

from mechanize.

Oops, closed inadvertently

from mechanize.

This is a bug with the server where the gzip content is cut off mid stream.

Firefox downloads this file using deflate, changing this to a feature request for deflate decoding

from mechanize.

deflate implemented

from mechanize.