Table Column Change issue, gives two columns in o/p
GoogleCodeExporter opened this issue · 9 comments
GoogleCodeExporter commented
Hi,
i am facing one issue while comparing HTML using daisydiff.
Seems to me that when i give simple two tables for comparison where difference
in data is in table columns then it throws additional column in o/p.Following
are steps to reproduce & attached screenshots of problem.
1: Give left side for comparison as
<table border=2><tr border=2><td border=2>column1</td><td
border=2>column2</td><td border=2>column3</td></tr><tr border=2><td
border=2>1</td><td border=2>2</td><td border=2>3</td></tr></table>
2: Give right side for comparison as
<table border=2><tr border=2><td border=2>column1</td><td
border=2>column2</td><td border=2>column3</td></tr><tr border=2><td
border=2>1</td><td border=2>22</td><td border=2>3</td></tr></table>
observe difference is in 2nd column's data for left side its 2 & for right its
22
What is the expected output? What do you see instead?
This results in addition of column (td) for final data which disturbs whole UI.
Expected output is such that either this should add additional column in header
columns or it should put difference data in single column
What version of the product are you using? On what operating system?
daisydiff 1.1 & Windows XP
Please provide any additional information below.
Attaching Screenshots for reference, this shift in column cuases large
usability issue
Original issue reported on code.google.com by ame...@gmail.com
on 9 Aug 2010 at 11:44
Attachments:
GoogleCodeExporter commented
Confirmed in DaisyDiff 1.1
Original comment by kkape...@gmail.com
on 10 Aug 2010 at 3:17
- Changed state: Accepted
- Added labels: ****
- Removed labels: ****
GoogleCodeExporter commented
Hi Kapelon,
thanks for accepting it as defect, when can i expect fix for this one? you guys are planning to fix this in DaisyDiff 1.2 version?
Original comment by ame...@gmail.com
on 10 Aug 2010 at 5:48
- Added labels: ****
- Removed labels: ****
GoogleCodeExporter commented
I can't really answer this question since I am not one of the core developers.
DaisyDiff seems to be in "maintainance" mode these days.
Speaking for myself only, I do not have the needed expertise/time to fix this
bug.
Original comment by kkape...@gmail.com
on 11 Aug 2010 at 9:00
- Added labels: ****
- Removed labels: ****
GoogleCodeExporter commented
There are currently no plans for a new release of DaisyDiff.
I'm the original developer, but I don't have the time anymore to work on
DaisyDiff. Ofcourse I would welcome a volunteer that can take things over.
Original comment by guy...@gmail.com
on 11 Aug 2010 at 9:27
- Added labels: ****
- Removed labels: ****
GoogleCodeExporter commented
[deleted comment]
GoogleCodeExporter commented
Hi, I'm happy to work on a fix for this as it affects me too. I'd appreciate
any input or suggestions from experienced committers as to the best heuristic
to use....
Original comment by joelhalb...@gmail.com
on 7 Dec 2010 at 4:29
- Added labels: ****
- Removed labels: ****
GoogleCodeExporter commented
I cannot really help you with the implementation part. However if you create a
patch that solves this issue and does not break anything else, we would be
happy to commit it in the official trunk!
Original comment by kkape...@gmail.com
on 7 Dec 2010 at 6:00
- Added labels: ****
- Removed labels: ****
GoogleCodeExporter commented
[deleted comment]
GoogleCodeExporter commented
http://code.google.com/p/daisydiff/issues/detail?id=28 seems to fix this.
Original comment by don.jp.w...@gmail.com
on 15 Jun 2011 at 5:30
- Added labels: ****
- Removed labels: ****