Forum: Ruby nokogiri 1.2.0 Released

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Aaron P. (Guest)
on 2009-02-23 06:23
(Received via mailing list)
nokogiri version 1.2.0 has been released!

* <>
* <>
* <>
* <>
* <

Nokogiri (鋸) is an HTML, XML, SAX, and Reader parser.


### 1.2.0 / 2008-02-22

* New features

  * CSS search now supports CSS3 namespace queries
  * Namespaces on the root node are automatically registered
  * CSS queries use the default namespace
  * Nokogiri::XML::Document#encoding get encoding used for this document
  * Nokogiri::XML::Document#url get the document url
  * Nokogiri::XML::Node#add_namespace add a namespace to the node LH#38
  * Nokogiri::XML::Node#each iterate over attribute name, value pairs
  * Nokogiri::XML::Node#keys get all attribute names
  * Nokogiri::XML::Node#line get the line number for a node (Thanks
Dirkjan Bussink!)
  * Nokogiri::XML::Node#serialize now takes an optional encoding
  * Nokogiri::XML::Node#to_html, to_xml, and to_xhtml take an optional
  * Nokogiri::XML::Node#to_str
  * Nokogiri::XML::Node#to_xhtml to produce XHTML documents
  * Nokogiri::XML::Node#values get all attribute values
  * Nokogiri::XML::Node#write_to writes the node to an IO object with
optional encoding
  * Nokogiri::XML::SAX::PushParser for all your push parsing needs.

* Bugfixes

  * Fixed Nokogiri::XML::Document#dup
  * Fixed header detection. Thanks rubikitch!
  * Fixed a problem where invalid CSS would cause the parser to hang

* Deprecations

  * Nokogiri::XML::Node.new_from_str will be deprecated in 1.3.0

* API Changes

  * Nokogiri::HTML.fragment now returns an XML::DocumentFragment (LH


* XPath support for document searching
* CSS3 selector support for document searching
* XML/HTML builder
* Drop in replacement for Hpricot (though not bug for bug)

Nokogiri parses and searches XML/HTML very quickly, and also has
correctly implemented CSS3 selector support as well as XPath support.

Here is a speed test:


Nokogiri also features an Hpricot compatibility layer to help ease the
to using correct CSS and XPath.


The Nokogiri mailing list is available here:


The bug tracker is available here:



  require 'nokogiri'
  require 'open-uri'

  doc =

  # Search for nodes by css
  doc.css('h3.r a.l').each do |link|
    puts link.content

  # Search for nodes by xpath
  doc.xpath('//h3/a[@class="l"]').each do |link|
    puts link.content

  # Or mix and match.'h3.r a.l', '//h3/a[@class="l"]').each do |link|
    puts link.content


* ruby 1.8 or 1.9
* libxml
* libxslt


* sudo gem install nokogiri

* <>
* <>
* <>
* <>
* <
Phlip (Guest)
on 2009-02-23 06:32
(Received via mailing list)
Aaron P. wrote:

> nokogiri version 1.2.0 has been released!

grabbed! Tx!
Phlip (Guest)
on 2009-02-23 06:50
(Received via mailing list)
Aaron P. wrote:

> nokogiri version 1.2.0 has been released!

The following is a question, if I got it wrong, and a code snippet if I

To add nokogiri to a Merb project's Cucumber featurizer, I...

Added it to features/support/env.rb:

   require "merb-core"
   require "spec"
   require "merb_cucumber/world/simple"
   require 'nokogiri'  # <-- with the correct style of quote 'ticks'!

Added its calls to features/steps/result_steps.rb

   When /^you go to (.*)/ do |text|
     @response = request(text)
     @xdoc = Nokogiri::HTML(@response.body.to_s)

   Then /^you should see an? (.+) element$/ do |searcher|
     @xdoc.css(searcher).should_not be_nil

Called its steps from features/comics.feature:

   Feature: serve webcomics

     Scenario: root page
       When you go to /
       Then you should see an img.comic element

The result is the usual bunch of pale green. (But note that I personally
suck at
writing customer-facing verbiage. They don't care if they see an img
with a
class of comic! They want to see a comic image! More verbiage tuning is
in order...)

Also note that I suck at writing RSpec matchers. The point of all this
is clear
error messages at fault time, and my .should_not be_nil is also not

So thanks for the lib! it's going to the top of my list from now on...
Phlip (Guest)
on 2009-02-23 07:31
(Received via mailing list)
>   Then /^you should see an? (.+) element$/ do |searcher|
>     @xdoc.css(searcher).should_not be_nil
>   end

Nooop. I forgot to test that in the negative - by changing the Then
and seeing if it fails cleanly. It did not, possibly because a failing
CSS hit
does not return a nil.

After changing to should_not be_blank, I then upgraded the verbiage in

   Then /^you should see an? (.+) (.+)$/ do |style, element|
     element = { 'image' => 'img' }.fetch(element, element)
     @xdoc.css("#{element}.#{style}").should_not be_blank


     When you go to /
     Then you should see a comic image

The {} is speculative coding; if I had a real client asking for these
they might write 'panel', which I must then translate to <div>...
Ryan D. (Guest)
on 2009-02-23 08:54
(Received via mailing list)
On Feb 22, 2009, at 20:49 , Phlip wrote:

>  require 'nokogiri'  # <-- with the correct style of quote 'ticks'!

This topic is locked and can not be replied to.