-
-
Notifications
You must be signed in to change notification settings - Fork 904
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Yet more JRuby issues when subclassing #702
Comments
@yokolet: Can all of the code that needs moving to make everything work properly with subclasses just be moved in one go? It seems somewhat pointless to just trickle these fixes out one at a time. |
It would be nice to run the entire nokogiri test suite against both an instance of XML::Node and an instance of a subclass thereof. |
@yokolet I'd be willing to offer a bounty to get this fix nudged up the queue a bit. Message me whatever you feel is reasonable - happy to help! |
@benlangfeld Sorry for my lateness to get you back. I fixed the issue in rev. 053c26f . Now, XML::Node has all methods implemented and its subclass works like Element. I think this commit is the last. @emcgee Thanks for the offer. But this bug fix doesn't deserve to a bounty since it is small and doesn't take much time. If you are willing to donate to Nokogiri project, I guess https://pledgie.com/campaigns/8187 is still working. |
@yokolet That's great. Can we get an RC please? |
Thanks a lot. Nokogiri 1.5.5 fixes ~100 spec failures on Blather. Now for EventMachine.... |
Aw, 100 spec failures... That's so sorry to have bothered you so much. I'm glad to hear the failures had gone away. |
Affected ruby versions
Affected nokogiri versions
Test case
Result
The text was updated successfully, but these errors were encountered: