Apache OpenOffice (AOO) Bugzilla – Issue 1083
Table with row of 0.01 height and no fit to size crashes Word and RTF filter
Last modified: 2003-09-08 16:56:16 UTC
Create text table with 4 rows, 3 columns. Put text into 1st, 2nd and 4th row. Leave 3rd row empty. Go to 3rd row. Choose Row-Height from context menu. Leave it at 0,01 and switch off fit to size. Saving as Word97/2000 or RTF crashes OOo. (BTW, the same applies to SO5.2)
Reassigned to Michael.
MRU->JP: I think it is not a problem of the filter. When creating a table like this, the non-pro throws the Assert "SvRect() ohne Width oder Height". Could it be, that a table with "forbidden" values is created with the way Dietrich Schulten described?
And the HTML export writes also wrong data.
changing QA contact from bugs@ to issues@
Problem is in the class SwWriteTable which create a tableline with more cells than the other lines defines. Because the SwWriteTableLine compare functions works with a ROWFUZZY value, so all lines with a line height less than 20 twips will be ignored. ->MIB please have a look to it
Seems to be my issue.
I have only seen this issuezilla bug now, so I haven't checked, but 98768 is probably similiar to this one. The changes made for 98768 might fix this crash. The code seems to want to ignore invisibly tall rows on export (which might make sense for html, but word export is happy with 0 height lines) but it ends up that the cells in the row are not ignored and get added to the next row. If the short row is the last row, then boom!. I wonder if we need a "fuzzy" line height match at all ?, I was unable to create an example table where I would need a fuzzy line height matcher.
There is no crash any longer
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.