Apache OpenOffice (AOO) Bugzilla – Issue 24069
Table gets displaced when jumping from disabling "online layout".
Last modified: 2013-08-07 14:38:26 UTC
Attached, a document with which the problem can be reproduced systematically. When the first page is showing up, notice how the table is place. Then, enable "View/Online Layout"; the table is properly placed. Now disable "View/Online Layout" to return to a print view and see how the table is misplaced. Saving the file and restarting swriter corrects the problem; the internals of the file does not seam to be affected, only the rendering data at runtime seam to be corrupted.
Created attachment 12243 [details] File to reproduce table displacement.
reassigend to jw
i do not know if i missunderstand what you named misplaced, but if i open your document for the first time, the table allready is misplaced. the last two columns of this table are not within the printable page area. if this what you mean? the document has the same look here before and after the online layout. if possible can you send me an screenshot of the looks one before one after and one while the onlinelayout. i will attach a scennshot of the document after loading it
Created attachment 12358 [details] screenshot of the document after loading it
Sorry. Yes, the table is already over the right margin (but not out of the print area; it prints well on paper). This is done on purpose because the table has to fit in this first page and it is already big. However, this is not the misplacement I am talking about. Follow my instructions and see if the table remains at the same place as it was the first time you opened it. It does not. That is the problem.
hmm as i wrote, here on my system the document looks after the change to and back from the online layout like before, i can not see any changes. the table is at the same position with the same look. i just opend it twice (second document is a copy of the first file) and i changed the first to ol and back and compared both looks -> nothing changed
Crap. I cannot reproduce the problem myself. This is sad. There is a looming bug that showed itself only on one particular day. I closed this ticket as Resolved-WorksForMe. If it reappears, I will re-open it.
thanks. wfm -> closed