Node.getLastCommonParent Algorithm

[daisydiff]

Node.getLastCommonParent Algorithm

[stevendwood]

I'm gonna close this off since no one has an opinion on it :) I believe the (or an) issue is that when looking for a place to put removed text we probably want to be less strict than TagNode.equals - e.g. it is correct that if I add an inline style or a class then the node should be different (so fails that test) in the two trees since the text within it will appear to have changed, however if I had also removed text, we would want the removed text to appear within the same tag and not the "last common parent" - so I think that the check needs to be relaxed in that instance.