Apache OpenOffice (AOO) Bugzilla – Issue 84564
Vertical alignment in a splitted table row initially wrong after opening document
Last modified: 2013-08-07 14:44:35 UTC
I searched for this one in the bug database, but could not find any related bug. I have a table with large (multi-line) rows in a Writer file. The vertical alignment in a cell at page breaks changes after reopening the file. In the given example, the second column has only one line, the third has multiple lines. If I allow page breaks in the table, then the text of the second column is aligned at the middle of the column of the first page, and does not show up in the rest of the same cell on the second page. This is what one would expect. But after reopening the document, the text in column 2 is suddenly aligned at the top of the cell--only after changing the alignment to top and then back to middle, the alignment is correct again.
Created attachment 50309 [details] Writer document with table illustrating this issue
MRU->FME: open attached document and see cell B3 lower on the page. The row breaks, thus it seems that the vertical cell alignment is initially calculated wrongly. It should be centered.
I've something simular. If I have a table with merged cells and more then one column where I want the text vertical centred. This works perfect as long the table is on one page. But as soon he split over another page, and I insert text or change someting in the last column, the text in the other cell is not centred anymore. To have it again centred, I need to align it first on top and then back centred.
Any news about this issue?
Sorry, no news on this.
Could you set a target milestone for a fix for this issue, please?
Well, this issue has a target: 3.x although not a very specific one. I'm sorry, but right now I cannot give you a better answer.
Could you at least define a specific target milestone? The issue is known over one and a half year now, and it is a basic one (happens with native open office documents, not only with Word documents).
Maybe at least a target milestone (3.3) to the second anniversary of this issue?