Daniel Barber

The dy attribute seems to be set on all tspans earlier in the function. I've had luck showing and hiding text elements with the following patch. It does not require...

Is there still an interest in this? For a project I am working on I had to add a parent attribute to nodes so I could walk back up the...

So, I have this working minus one key aspect, which is what to do with a few properties that are set for each element when the document is parsed and...

You can track the progress on this branch: https://github.com/aleph1/xmldoc/tree/aleph1-node-manipulation

`options.readonly` sounds good, but the only issue with having it `false` by default is that it will be a breaking change if anyone is using the `line`, `column`, `position`, and...

One other related question. Currently `XmlElement.eachChild` iterates through children in a forward direction. This can cause an issue if one tries to mutate the children array during iteration. So, this...

More updates have been made on that branch. A few notes: - XmlElement.eachChild now operates on a copy of element.children but all tests still pass - the 'tag locations' test...

I've added the following to this branch: https://github.com/aleph1/xmldoc/tree/aleph1-node-manipulation - Clone support for each node type - Empty method for XmlElement - Modified how XmlElement is created to allow for manual...

3. I will have this throw an error. Though I might recommend an `XmlDocument.toXmlElement` function that removes this extraneous data, or a `XmlDocument.cloneAsXmlElement` function so the original `XmlDocument` is maintained....

The only issue I can see with my original approach and how descendant paths are implemented at present is that the “.” (period) is allowed in XML tag names. Would...