https://bugs.documentfoundation.org/show_bug.cgi?id=159029
--- Comment #4 from William Friedman <will.fried...@gmail.com> ---
Stephane, I was about to upload a test document, so thank you for saving me the
time.
I was playing around with your document, and noticed a new wrinkle. To make
this less wordy, I'm going to use "hello" to refer to the top merged cell and
"goodbye" to refer to the bottom merged cell. After step 12:
13. Delete the last remaining line before the table. This causes the "goodbye"
cell to span onto the first page. "Hello" jumps to the bottom of the column
(correctly!), while "goodbye" jumps to the top (incorrectly).
14. Hit ctrl-Z or insert a new line before the table. Now both "hello" and
"goodbye" are fully on their own pagess. "Hello" stays the bottom (correctly!),
and "goodbye" jumps back to the bottom (correctly!).
15. Insert another new line before the table. "Hello" now spans two pages, and
its text jumps back to the top. "Goodbye" remains correctly bottom-aligned.
16. Hit ctrl-Z. Despite the fact that "hello" is now back on one page, its text
remains stuck at the top. "Goodbye" remains correctly at the bottom.
It seems from this that the bottom alignment of the top merged cell ("hello")
is recalculated when the bottom merged cell ("goodbye") starts to appear on the
first page, but *not* when the top merged cell stops spanning two pages. Once
the bottom alignment is recalculated, though it "sticks" until the merged cell
spans two pages again. But, interestingly, the bottom merged cell ("goodbye")
*does* recalculate correctly *immediately after* it stops spanning two pages,
which does not happen immediately when the top merged cell stops spanning two
pages.
--
You are receiving this mail because:
You are the assignee for the bug.
