Hi, Today I've managed to get the DOM treebuilder and treewalker to work with DOM implementations apart from minidom. The treebuilder is almost identical to ETree one (in terms of getting a DOM treewalker for the given impl), and also provides various means (in treebuilders.__init__ and the very end of treebuilders.dom) of backwards compatibility: I haven't actually changed any of the test cases, so they still use minidom and still all pass.
The work was completed in r1099 which removed the setting a read-only DOM property when using anything apart from minidom (this is needed to work around a bug in minidom, but causes issues in any DOM implementation that enforces the fact it's read-only), and in r1100 I committed test cases for pxdom — this causes one failure and one error, both down to a bug in pxdom (in short, pxdom attempts to enforce XML well-formness requirements within the DOM, and throws an exception when trying to set something that is expressible in text/ html but not in XML — the author has been informed). The treewalker is already suitable for other DOM implementations and so wasn't changed, though the error is caused by the above issue with pxdom, triggered by one of the treewalker test cases (whereas the failure is caused by a treebuilder test case). -- Geoffrey Sneddon <http://gsnedders.com/> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "html5lib-discuss" group. To post to this group, send email to html5lib-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/html5lib-discuss?hl=en-GB -~----------~----~----~----~------~----~------~--~---
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4