https://bugs.documentfoundation.org/show_bug.cgi?id=158227

Stéphane Guillou (stragu) <stephane.guil...@libreoffice.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |108519, 103100
                 OS|Windows (All)               |All
                 CC|                            |stephane.guillou@libreoffic
                   |                            |e.org
            Version|7.6.2.1 release             |Inherited From OOo
            Summary|Broken undo history with    |Broken undo history with
                   |multiple columns and table  |table and (page or column)
                   |at the page beginning       |break
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=15
                   |                            |8226

--- Comment #5 from Stéphane Guillou (stragu) 
<stephane.guil...@libreoffice.org> ---
Reproduced as described, even without step 3, in:

Version: 7.6.3.2 (X86_64) / LibreOffice Community
Build ID: 29d686fea9f6705b262d369fede658f824154cc0
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 5589659829f8a1cef8ca1c8a468732105bbe231b
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

as well as OOo 3.3, so issue is inherited.

The same issue can be reproduced with no columns, a table and a page break. So
I would say it's the interaction between table and break.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103100
[Bug 103100] [META] Writer table bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=108519
[Bug 108519] [META] Page break bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to