Issues - tenderlove/nokogiri

tenderlove / nokogiri

675

Description:

Nokogiri (鋸) is an HTML, XML, SAX, and Reader parser with XPath and CSS selector support.

Sort by: Priority | Votes | Last Updated

Loading…

161.

0 votes

1.4.1
x

push parser needs fixin'
1 comment Created 9 days ago by tenderlove

Title

Body
http://gist.github.com/232170
or cancel

http://gist.github.com/232170

Comments

astro Sat Nov 14 06:24:25 -0800 2009 | link

Commit bfa172d allows to set the RECOVER option for PushParser. This resolves the issue.

Comment
Commit bfa172d4a2896e526ce39088af9cfd436d72203c allows to set the RECOVER option for PushParser. This resolves the issue.
or cancel

Parsed with GitHub Flavored Markdown
165.

0 votes

1.4.1
x

Provide DOM/SAX examples of loading a DTD so named entities can be resolved
0 comments Created 7 days ago by yob

Title

Body
Currently if I attempt to parse a document that has named entities in it I get an exception. The files I'm trying to parse conform to a DTD that defines the valid entities, word on the street is that by loading the DTD i may be able to avoid the exception. See http://groups.google.com/group/nokogiri-talk/browse_thread/thread/8225dfb0ffbe0098
or cancel

Currently if I attempt to parse a document that has named entities in it I get an exception.

The files I'm trying to parse conform to a DTD that defines the valid entities, word on the street is that by loading the DTD i may be able to avoid the exception. See http://groups.google.com/group/nokogiri-talk/browse_thread/thread/8225dfb0ffbe0098

Comments

Parsed with GitHub Flavored Markdown
164.

0 votes

1.4.1
x

Add some of these methods
0 comments Created 7 days ago by tenderlove

Title

Body
http://gist.github.com/227705
or cancel

http://gist.github.com/227705

Comments

Parsed with GitHub Flavored Markdown
167.

0 votes

1.4.1
x

The SOAP adapter is busted
1 comment Created 5 days ago by tenderlove

Title

Body
I added the xmldecl method to the SAX callbacks, and that broke the SOAP adapter. That broken this dudes code: http://groups.google.com/group/nokogiri-talk/msg/dca72612114cfcc5 We need to figure out a way to get the adapter under test *without* loading in soap4r
or cancel

I added the xmldecl method to the SAX callbacks, and that broke the SOAP adapter. That broken this dudes code:

http://groups.google.com/group/nokogiri-talk/msg/dca72612114cfcc5

We need to figure out a way to get the adapter under test without loading in soap4r

Comments

flavorjones Tue Nov 17 23:38:16 -0800 2009 | link

I've pushed a branch named 'soap4r-bug' that reproduces this problem in the Nokogiri test suite.

Comment
I've pushed a branch named 'soap4r-bug' that reproduces this problem in the Nokogiri test suite.
or cancel

Parsed with GitHub Flavored Markdown
166.

0 votes

1.4.1
x

XML::Namespace#inspect may be broken
0 comments Created 5 days ago by tenderlove

Title

Body
I *think* the inspect method is broken. Broken or not, we need to figure out this crash: http://groups.google.com/group/nokogiri-talk/msg/6f8e4ac93fbebf39
or cancel

I think the inspect method is broken. Broken or not, we need to figure out this crash:

http://groups.google.com/group/nokogiri-talk/msg/6f8e4ac93fbebf39

Comments

Parsed with GitHub Flavored Markdown
104.

0 votes

1.4.1
x

tenderlove
x

Figure out how to attach a DTD to a document
0 comments Created 3 months ago by tenderlove

Title

Body
I would like to be able to attach a DTD to an HTML document so that the id() xpath function works.
or cancel

I would like to be able to attach a DTD to an HTML document so that the id() xpath function works.

Comments

Parsed with GitHub Flavored Markdown
156.

0 votes

1.4.1
x

tenderlove
x

" is nice
1 comment Created 17 days ago by david

Title

Body
I don't know if this really a bug or if I'm being really stupid, but here goes: So, when you have a double quote character inside your attribute value, nokogiri does this attribute='a string with a double " quote' Unfortunately, this is making the xerces java parser (or whatever parser Openfire uses) throw a hissy fit. While I understand this may be a xerces bug (OWPOU), not a nokogiri one, it would still be nice if we could have the option of using attribute="a string with a double &quot; quote" (I tried using send(:native_content=, "...") but that has the same result.
or cancel
I don't know if this really a bug or if I'm being really stupid, but here goes:

So, when you have a double quote character inside your attribute value, nokogiri does this

attribute='a string with a double " quote'

Unfortunately, this is making the xerces java parser (or whatever parser Openfire uses) throw a hissy fit. While I understand this may be a xerces bug (OWPOU), not a nokogiri one, it would still be nice if we could have the option of using

attribute="a string with a double " quote"

(I tried using send(:native_content=, "...") but that has the same result.

Comments
tenderlove Mon Nov 09 15:41:15 -0800 2009 | link
What version of libxml2 are you using? Past the contents of this command, if you can:

$ nokogiri -v

Also, if you could post the code to reproduce this, that would be great. So far, libxml2 is behaving how you want it to:

d = Nokogiri::XML('<root />') d.root['foo'] = 'hello " world' puts d.to_xml # => '<root foo="hello " world"/>'
Comment
What version of libxml2 are you using? Past the contents of this command, if you can: $ nokogiri -v Also, if you could post the code to reproduce this, that would be great. So far, libxml2 is behaving how you want it to: d = Nokogiri::XML('<root />') d.root['foo'] = 'hello " world' puts d.to_xml # => '<root foo="hello " world"/>'
or cancel
Parsed with GitHub Flavored Markdown
46.

0 votes

tenderlove
x

Documentation overhaul
3 comments Created 6 months ago by flavorjones

Title

Body
We might want to write up some docs that present functionality broken down the same way that jQuery's docs do it (which I find totally useful and obvious): * core (parsing) * selectors * attributes * traversing * manipulation
or cancel
We might want to write up some docs that present functionality broken down the same way that jQuery's docs do it (which I find totally useful and obvious):
- core (parsing)
- selectors
- attributes
- traversing
- manipulation
Comments

tenderlove Fri May 15 09:39:55 -0700 2009 | link

I like this. Should we do it in the wiki? Or as RDoc? Or both?

Comment
I like this. Should we do it in the wiki? Or as RDoc? Or both?
or cancel

JESii Sat Nov 07 05:59:04 -0800 2009 | link

I'd say both of them... with the hpricot api seemingly unavailable following why's disappearance, better / more complete documentation for nokogiri would be a great help.

Comment
I'd say both of them... with the hpricot api seemingly unavailable following why's disappearance, better / more complete documentation for nokogiri would be a great help.
or cancel

tenderlove Sat Nov 07 12:23:39 -0800 2009 | link

We're doing our best. All methods are currently documented. Unfortunately "better" is a very subjective word. That being said, patches are greatly appreciated!

We've launched a new website: http://nokogiri.org

And we're working on tutorials. :-(

Comment
We're doing our best. All methods are currently documented. Unfortunately "better" is a very subjective word. That being said, patches are greatly appreciated! We've launched a new website: http://nokogiri.org And we're working on tutorials. :-(
or cancel

Parsed with GitHub Flavored Markdown
48.

1 vote

ffi
x

mdalessio
x

FFI ruby object caching should be rewritten to not use id2ref
3 comments Created 6 months ago by flavorjones

Title

Body
id2ref is slow and may be turned off by default in JRuby 1.4. discussed with wmeissner, and the probable path is to build an API into FFI that is an hash table containing address => weakref(ruby_object).
or cancel

id2ref is slow and may be turned off by default in JRuby 1.4.

discussed with wmeissner, and the probable path is to build an API into FFI that is an hash table containing address => weakref(ruby_object).

Comments

nicksieger Mon Nov 16 13:32:31 -0800 2009 | link

FYI, id2ref (and objectspace) is turned off by default in JRuby. We made a conscious decision to do this because it's expensive and not feasible to manage all live objects with JRuby.

Comment
FYI, id2ref (and objectspace) *is* turned off by default in JRuby. We made a conscious decision to do this because it's expensive and not feasible to manage all live objects with JRuby.
or cancel

nicksieger Mon Nov 16 13:59:28 -0800 2009 | link

Also: tools to help implement the caching in Java/JRuby:

http://java.sun.com/javase/6/docs/api/java/lang/ref/WeakReference.html
http://java.sun.com/javase/6/docs/api/java/util/WeakHashMap.html

Note the last item may not be exactly what is needed, it's a map w/ weak keys, not a map that weakly references its values.

Comment
Also: tools to help implement the caching in Java/JRuby: http://java.sun.com/javase/6/docs/api/java/lang/ref/WeakReference.html http://java.sun.com/javase/6/docs/api/java/util/WeakHashMap.html Note the last item may not be exactly what is needed, it's a map w/ weak keys, not a map that weakly references its values.
or cancel

flavorjones Mon Nov 16 14:07:16 -0800 2009 | link

Nick, thanks for the pointers (no pun intended).

Comment
Nick, thanks for the pointers (no pun intended).
or cancel

Parsed with GitHub Flavored Markdown
51.

0 votes

ffi
x

mdalessio
x

FFI: support varargs in error/exception callbacks
1 comment Created 6 months ago by flavorjones

Title

Body
we should open JIRA tickets for vararg support in FFI callbacks then we should format the libxml error messages properly in the error/exception callbacks
or cancel

we should open JIRA tickets for vararg support in FFI callbacks

then we should format the libxml error messages properly in the error/exception callbacks

Comments

flavorjones Sun Jun 21 19:38:17 -0700 2009 | link

@tmm1 poked me about this. I'll open a ticket for it tonight.

Comment
@tmm1 poked me about this. I'll open a ticket for it tonight.
or cancel

Parsed with GitHub Flavored Markdown
65.

0 votes

ffi
x

mdalessio
x

use get_array_of_pointer for performance improvement
0 comments Created 5 months ago by flavorjones

Title

Body
should be in JRuby 1.3 final, not sure about MRI-FFI right now. in particular, this can be used in SAX parser implementation.
or cancel

should be in JRuby 1.3 final, not sure about MRI-FFI right now. in particular, this can be used in SAX parser implementation.

Comments

Parsed with GitHub Flavored Markdown
106.

0 votes

ffi
x

mdalessio
x

FFI needs unlinkedNodes to be optimized
0 comments Created 3 months ago by flavorjones

Title

Body
Extension commit f34f3bd needs to be ported.
or cancel

Extension commit f34f3bd needs to be ported.

Comments

Parsed with GitHub Flavored Markdown
168.

0 votes

The Tutorials link is broken on Firefox (including when JavaScript is enabled)
0 comments Created 5 days ago by shlomif

Title

Body
Hi all! The tutorials link on the Nokogiri site is broken on Firefox 3.5.5 on Mandriva Linux Cooker (standard Mandriva package), even when JavaScript is enabled (and it should work even when it isn't.). I don't see anything in the error console. Please fix it. Regards, -- Shlomi Fish
or cancel

Hi all!

The tutorials link on the Nokogiri site is broken on Firefox 3.5.5 on Mandriva Linux Cooker (standard Mandriva package), even when JavaScript is enabled (and it should work even when it isn't.).

I don't see anything in the error console.

Please fix it.

Regards,

-- Shlomi Fish

Comments

Parsed with GitHub Flavored Markdown
172.

0 votes

Extending nokogiri with jQuery selectors?
0 comments Created 1 day ago by jeroenvandijk

Title

Body
I'm using nokogiri through webrat to assert whether elements exist. The set of css3 selectors are limited if you compare them with the set selectors of jquery (.e.g. :has, :contains). So I have the following questions: * is there a plan to make nokogiri compatible with jquery? * if not, would it be hard to fork nokogiri and add the selectors? Any hints where to start? Here is an example that illustrates the problem I have http://groups.google.nl/group/formtastic/msg/2601ac08d8c48a96
or cancel
I'm using nokogiri through webrat to assert whether elements exist. The set of css3 selectors are limited if you compare them with the set selectors of jquery (.e.g. :has, :contains). So I have the following questions:
- is there a plan to make nokogiri compatible with jquery?
- if not, would it be hard to fork nokogiri and add the selectors? Any hints where to start?
Here is an example that illustrates the problem I have http://groups.google.nl/group/formtastic/msg/2601ac08d8c48a96
Comments

Parsed with GitHub Flavored Markdown