Issue 52 in daisydiff: An element that was moved out of a table can lead to broken table elements in the diff

[codesite...@google.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 52 by christop...@gmail.com: An element that was moved out of a
table can lead to broken table elements in the diff
http://code.google.com/p/daisydiff/issues/detail?id=52

What steps will reproduce the problem?
1. Using the old.html and new.html files attached, call "java -jar
daisydiff.jar old.html new.html"
This produces the attached daisydiff.html

What is the expected output? What do you see instead?
The produced daisydiff.htm contains a <td> Element that is outside of any
<table>.
In my case the "abc" String should not have been moved out of table.

What version of the product are you using? On what operating system?
daisydiff 1.2 running on osx


Attachments:
old.html 80 bytes
new.html 11 bytes
daisydiff.htm 2.1 KB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[codesite...@google.com]

Comment #1 on issue 52 by henrythe...@gmail.com: An element that was moved

out of a table can lead to broken table elements in the diff
http://code.google.com/p/daisydiff/issues/detail?id=52

A workaround (until fixed) is to use jSoup (jsoup.org) to parse the
resultant output from DaisyDiff into a jSoup Document object and then
toString() that to generate a clean HTML string. jSoup will clean up any
erroneous elements in the document.

eg:
docObj = jSoup.parse(diff_HTML);
return docObj.toString();