Bug 134257 - FILEOPEN DOCX Paragraph “spacing before” not ignored after page break
Summary: FILEOPEN DOCX Paragraph “spacing before” not ignored after page break
Status: RESOLVED DUPLICATE of bug 153964
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks: DOCX-Paragraph Paragraph-Spacing
  Show dependency treegraph
 
Reported: 2020-06-23 10:44 UTC by NISZ LibreOffice Team
Modified: 2023-03-24 13:38 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file from Word (11.53 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2020-06-23 10:44 UTC, NISZ LibreOffice Team
Details
Screenshot of the original document side by side in Word and Writer (93.48 KB, image/png)
2020-06-23 10:44 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2020-06-23 10:44:07 UTC
Created attachment 162341 [details]
Example file from Word

Attached document contains a paragraph formatted as Heading 1.
This has a 24 pt Spacing Before in Word, and at the top of the first page Word displays the paragraph with this much spacing before.
The second page starts after a page break with a similar Heading 1 style paragraph.
Word however does not display the paragraph with any spacing before.
Writer on the other hand displays the spacing before in both cases. 
In the original document we had this difference led to a page layout change, since the content no longer fitted on just one page.

Steps to reproduce:
    1. Open attached document

Actual results:
Spacing before the second paragraph is displayed.

Expected results:
Spacing before the second paragraph should not be displayed. At least not in Word-made documents.

LibreOffice details:
Version: 7.1.0.0.alpha0+ (x64)
Build ID: 642fc41cd7d080384658e10b30bb9d3b38a2cbd9
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
Locale: hu-HU (hu_HU); UI: en-US
Calc: CL

Also happens all the way back to
LibreOffice 3.5.0rc3 
Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d5373
Comment 1 NISZ LibreOffice Team 2020-06-23 10:44:27 UTC
Created attachment 162342 [details]
Screenshot of the original document side by side in Word and Writer
Comment 2 Dieter 2020-06-26 14:05:20 UTC
I confirm it with

Version: 7.0.0.0.beta2 (x64)
Build ID: 1c213561a365b5666167321de68c9977500c9612
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL
Comment 3 NISZ LibreOffice Team 2021-08-09 11:43:22 UTC
Note: there is a compatibility option on Options - Writer - Compatibiltiy "Add paragraph and table spacing at tops of pages" that is enabled by default.
Turning this off makes Writer ignore the spacing before the paragraphs in this document, however not only for the second pages paragraph, but for the first too.

Maybe we should just modify this option to not work for the very first page of the document.
Comment 4 Justin L 2021-08-27 09:21:11 UTC
(In reply to NISZ LibreOffice Team from comment #3)
> Maybe we should just modify this option to not work for the very first page
> of the document.
Likely this would be a "per section", so not quite as simple as first page only. You would want to test fairly exhaustively before modifying an existing option.
Comment 5 Gabor Kelemen (allotropia) 2023-03-24 12:19:14 UTC
Hm, this seems to be fixed now in master, after

https://git.libreoffice.org/core/+/96a502b3756a1c100b40235f50ef2122d5b543f9

author	Justin Luth <justin.luth@collabora.com>	Tue Mar 07 07:43:14 2023 -0500
committer	Justin Luth <jluth@mail.com>	Wed Mar 08 12:25:57 2023 +0000

tdf#153964 writerfilter compat15: top margin after break split

Also related bugs example document looks as expected/described in:
https://bugs.documentfoundation.org/show_bug.cgi?id=126677#c14

Thanks Justin for fixing this!

*** This bug has been marked as a duplicate of bug 153964 ***