Description: Part of the table lost/ re-layouting after clicking inside a table Steps to Reproduce: 1. Open attachment 159360 [details] 2. Scroll down to the bottom (notice full table is visible 3. Scroll to page 2 (and click inside the table (layout changes) 4. Scroll down to the bottom (part of table is cut off) Actual Results: Clicking inside the table causes re-layouting which makes a part of last page table invisible Expected Results: Not Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.0.0.alpha0+ (x64) Build ID: 4501a0ba623ad61c5a4e0b807da2e96f0e4ce82c CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
I think there is a problem with the document. Enable formatting marks. You can see, that there are several cells without a paragraph mark (last cells on page 2, last cells on page 3 and perhaps some more). If I click in such a cell, the cell expands.
(In reply to Dieter from comment #1) > I think there is a problem with the document. Enable formatting marks. You > can see, that there are several cells without a paragraph mark (last cells > on page 2, last cells on page 3 and perhaps some more). If I click in such a > cell, the cell expands. The document itself is 'fine'; created with LibreOffice. It's hard to get a broken - saved - file which behaves the same as unsaved one. It's more or less developers hell. Embedded table splitting is hard, multi-page, cross table, with weird paragraphs. A perfect layout = Layout loop. Stopping lay-outing to soon (shifting tables, of page content). Combine it footnotes and everything will be even more fun. It does happen in 'actual' documents too - to some extent - but not in this scale. More a 'proof of concept'. This linger around to check once in a while.. Nice for crash testing and testing layout performance (there are still some table layout loops; if somebody going to work on that.. this bug will be affected too (I think) So expect it more to float around
*** This bug has been marked as a duplicate of bug 128437 ***