Bug 149564 - FILEOPEN DOCX Large frame in header overlaps frame in footer
Summary: FILEOPEN DOCX Large frame in header overlaps frame in footer
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks: DOCX-Header-Footer
  Show dependency treegraph
 
Reported: 2022-06-14 16:37 UTC by Gabor Kelemen (Collabora)
Modified: 2026-07-03 03:13 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
The example file in Word 2016 and Writer master with the footer (103.80 KB, image/png)
2022-06-14 16:37 UTC, Gabor Kelemen (Collabora)
Details
strace log 149564 (25.01 KB, text/plain)
2022-06-20 06:41 UTC, vis_qa
Details
screenshot 149564 (100.64 KB, image/jpeg)
2022-06-20 06:43 UTC, vis_qa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gabor Kelemen (Collabora) 2022-06-14 16:37:34 UTC
Created attachment 180764 [details]
The example file in Word 2016 and Writer master with the footer

This is a continuation of bug 149563

The table content of the header in attachment 180759 [details] is very tall, so much that it overlaps the content in the footer.
The header and footer have negative page margin set, so their content is imported into textframes. However the Z-order of these textframes is incorrect. 
In Word the footer content overlaps the header content, while in Writer the header content overlaps the footer content.

1, Open attachment 180759 [details] 
2, Notice that the blue background table in the footer is barely visible in Writer, but fully visible in Word.

This started in 7.2 with fixing of bug 119952 - before these were not even visible, so differently bad.

Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: c0e66cfab12d6c78d68af09498533362724dbd05
CPU threads: 14; OS: Windows 10.0 Build 19044; UI render: default; VCL: win
Locale: en-US (hu_HU); UI: en-US
Calc: threaded
Comment 1 vis_qa 2022-06-20 06:40:22 UTC
reproduce:

Version: 7.3.4.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 4; OS: Linux 3.18; UI render: default; VCL: x11
Locale: en-US (C); UI: en-US
Debian package version: 1:7.3.4~rc2-1
Calc: threaded

* attaching screenshot, strace (if wrong, let me know ;))
Comment 2 vis_qa 2022-06-20 06:41:36 UTC
Created attachment 180844 [details]
strace log 149564
Comment 3 vis_qa 2022-06-20 06:43:13 UTC
Created attachment 180845 [details]
screenshot 149564
Comment 4 Buovjaga 2024-07-02 11:41:38 UTC
Still confirmed

Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: cc1f1e0e6dcabee2b6ca28f4f1341f0099814966
CPU threads: 8; OS: Linux 6.9; UI render: default; VCL: kf6 (cairo+wayland)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: CL threaded
Comment 5 QA Administrators 2026-07-03 03:13:51 UTC
Dear Gabor Kelemen (allotropia),

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug