Bug Hunting Session
Bug 120646 - Handling of columns in section not correct
Summary: Handling of columns in section not correct
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.2.1 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, possibleRegression
: 120645 (view as bug list)
Depends on:
Blocks: Page-Layout-Columns
  Show dependency treegraph
 
Reported: 2018-10-16 16:26 UTC by Wilfried Koch
Modified: 2019-07-08 14:50 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Original file (19.08 MB, application/vnd.oasis.opendocument.text)
2018-10-16 16:31 UTC, Wilfried Koch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wilfried Koch 2018-10-16 16:26:03 UTC
Description:
In an existing document page ranges are not handled correctly.
The error does not show in newly created files.


A newly added range always takes the full available space, not only the space needed. 
In file Short with ranges.odt the Limit is by the Picture on page 2 and by the page border on page 4.

There is no equal distribution of text between the columns

Steps to Reproduce:
1.Just enter a new page range
2.
3.

Actual Results:
Range taking the whole page (page 4)

Expected Results:
Range with two columns of same length, ending somewhere in the middle of the page


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Wilfried Koch 2018-10-16 16:31:36 UTC
Created attachment 145768 [details]
Original file
Comment 2 Oliver Brinzing 2018-10-16 16:36:21 UTC
*** Bug 120645 has been marked as a duplicate of this bug. ***
Comment 3 Wilfried Koch 2018-10-18 16:03:54 UTC
Works correctly in 5.1.6.2 (Win 64)
Comment 4 Dieter Praas 2018-10-19 18:41:45 UTC
I'm sorry Wilfried, but I don't know what you mean with "page range" and I also couldn't find it in the help-index. So I don't understand your steps to reproduce. When I open your document with LO master, everything looks fine to me on pages 2 and 4.
Comment 5 Wilfried Koch 2018-10-19 19:49:09 UTC
Concerning the terms: I used page range = (Seiten-) Bereich resp. Bereich in German.

Meanwhile I have the following workaround: I create the range (Bereich) in 5.1.6.2. Faulty ranges are corrected and recreated if necessary.


Generally I work in 6.1.3.1. now. This is due to Speed reasons for the 300 page document. I don't touch the ranges in 6.1.3.1. and everything is OK. When I make changes here (e. g. changing the number of coulumns forth and back) there is often (maybe not always) a wrong appearance of the range.

If you feel it could be helpful, I will care for screenshots, but that could take some time.

Question: What stands LO (LibreOffice I assume) >> master << for?
Comment 6 Dieter Praas 2018-10-20 06:41:10 UTC
Thank you for clarification:

Steps to reproduce:
1. Open attachment from comment 1
2. Put cursor before image on page 2
3. Insert => Section => Columns => 2 columns =>Insert

actual result:
2 columns until the end of the page
If you enter a 2 column section at the beginning of a page, column covers the the whole page. 

Expected result:
Only one line like a section with one column.

Wilfried, does this decscribe your problem? I'm sure that such a bugreport already exists, but I couldn't find it.

I used

Version: 6.2.0.0.alpha0+ (x64)
Build ID: 48cfa0b00b22f11ade53aec79b2fdddad253e1bd
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-03_02:01:42
Locale: en-US (de_DE); Calc: CL

and

Version: 6.0.6.2 (x64)
Build-ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: group
Comment 7 Wilfried Koch 2018-10-20 15:44:42 UTC
The description of the bug is OK.

Thank you
Comment 8 Dieter Praas 2018-10-21 11:34:09 UTC
(In reply to Wilfried Koch from comment #7)
> The description of the bug is OK.

=> NEW
Comment 9 Wilfried Koch 2019-07-08 08:07:27 UTC
The bug seems to be not present in 6.0.0.1