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

            Bug ID: 162027
           Summary: FILEOPEN DOCX: empty header should apply only page
                    margin, not the header-from-top margin (problem with
                    different-first)
           Product: LibreOffice
           Version: 24.2.0.0 alpha0+
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Keywords: bibisected, bisected, regression
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected], [email protected]
            Blocks: 161381

This is just re-opening LO 7.2 bug 135217. The unit test for it
(writerfilter/dmapper/follow-page-top-margin.docx) was changed to be a 1.25cm
margin instead of a very minimal 0.25cm margin, in order to allow a patch to be
merged.

This is due to fundamental header/footer differences between MSO and LO. Now
that we don't use two page styles for first/follow, we have lost the ability to
emulate an enabled first header and disabled follow header.

margin.docx (attachment 154527): has a 0.25cm top page margin set with some
header contents on the first page and no header contents on the second. So the
first page is supposed to apply the "header from top" value of 1.25cm, while
the second page is supposed to ignore all that and just use the page margin
settings.

attachment 163682: Screenshot of the margin.docx side by side in Word and
Writer

The 24.2 regression comes from author Tomaž Vajngerl on 2023-12-01 08:26:38
with commit 4b0fa253a4540f5461397815d290586f9ddabe61 
    tdf#136472 adjust ooxml import to handle first header/footer
https://gerrit.libreoffice.org/c/core/+/157860


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=161381
[Bug 161381] [META] Regressions from "tdf#136472 adjust ooxml import to handle
first header/footer"
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to