Download it now!
Bug 107497 - top border padding produces additional top margin if paragraph is first in section
Summary: top border padding produces additional top margin if paragraph is first in se...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Writer-Master-Doc Writer-Styles-Paragraph
  Show dependency treegraph
 
Reported: 2017-04-28 08:54 UTC by Regina Henschel
Modified: 2020-09-27 15:34 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Erroneous margin at top of section (16.36 KB, application/vnd.oasis.opendocument.text)
2017-04-28 08:54 UTC, Regina Henschel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Regina Henschel 2017-04-28 08:54:57 UTC
Created attachment 132924 [details]
Erroneous margin at top of section

If a paragraph style sets a top "Spacing to Content" in tab "Borders", then the paragraph gets an additional top margin, if it is used as first paragraph in a section. This gives problems in master documents, because the child document it always put in a section.

Open attached document. It contains a paragraph style "Text body Border" with blue background. All margin settings in the tab "Indent&Spacing" are 0cm and line spacing is "single". So the paragraphs should follow each other without margins.
Notice, that the first paragraph in the section has an additional top margin. If you change the top border spacing from 3cm to another value, you will notice, that this is directly reflected to this margin.
The spacing between border and content is a padding and must not have any influence on margins.
Comment 1 Regina Henschel 2017-04-28 11:04:01 UTC
I forgot: Save the document and reload it to make the changes visible.
Comment 2 Jacques Guilleron 2017-04-28 13:46:02 UTC
Hi Regina,

Reproduced with
LO 5.4.0.0.alpha0+
Build ID: 3a36cf434fb4a967c9ea767cb7ac5f4da0502a0d
CPU threads: 2; OS: Windows 6.1; UI render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2017-04-28_06:33:58
Locale: fr-FR (fr_FR); Calc: CL
also with
LO 3.5.3.2 Version ID : 235ab8a-3802056-4a8fed3-2d66ea8-e241b80

so probably inherited from OOo.
Comment 3 QA Administrators 2018-10-11 03:03:24 UTC Comment hidden (obsolete)
Comment 4 Regina Henschel 2018-10-11 07:50:51 UTC
The error still exists in Version: 6.2.0.0.alpha0+ (x64)
Build ID: d9ad59da50c1172fe98f94370221c9c1b688200a
CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-09_01:03:44
Locale: de-DE (en_US); Calc: CL
Comment 5 QA Administrators 2019-10-12 02:43:48 UTC Comment hidden (obsolete)
Comment 6 Regina Henschel 2019-10-12 20:34:49 UTC
The error still exists in Version: 6.4.0.0.alpha0+ (x64)
Build ID: b2d8093b19642038631dfb8f1ab6745a380a652c
CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2019-09-23_22:42:37
Locale: de-DE (en_US); UI-Language: en-US
Calc: threaded