Bug 122282 - SectPr nextColumn section break doesn't connect to the previous columns
Summary: SectPr nextColumn section break doesn't connect to the previous columns
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks: Page-Layout-Columns DOCX-Page
  Show dependency treegraph
 
Reported: 2018-12-22 16:54 UTC by Justin L
Modified: 2025-05-18 03:11 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
n652364.docx: just open this one page document in LibreOffice (8.76 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2018-12-22 16:54 UTC, Justin L
Details
n652364.pdf: as seen by Word 2010 (81.99 KB, application/pdf)
2019-01-03 07:34 UTC, Justin L
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Justin L 2018-12-22 16:54:08 UTC
Created attachment 147778 [details]
n652364.docx: just open this one page document in LibreOffice

Handling a manual column break is easy. Handling a section column break is hard because this is completely different from LibreOffice's use of sections. The previous section will need to be expanded to encompass this section.

I'm not sure what the purpose is of having one column be in a different section than another column in Microsoft office, but fortunately there don't seem to be many examples of them. Likely this is a new capability, because I don't see how to create this in Word 2003.

This document ought to be a single page, and the two Text 1 entries should be in column 1 while the two Text2 entries should be in column 2.

Instead, Text1 is balanced across both columns, and then there is a page break before the pair of Text 2 entries - which are no longer in columns.
Comment 1 Durgapriyanka 2019-01-02 20:48:48 UTC
Thank you for reporting the bug. I can confirm that the bug is present in 

Version: 6.3.0.0.alpha0+
Build ID: 3c964980da07892a02d5ac721d80558c459532d0
CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-12-12_02:07:45
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
Comment 2 Justin L 2019-01-03 07:34:47 UTC
Created attachment 147968 [details]
n652364.pdf: as seen by Word 2010
Comment 3 QA Administrators 2021-01-03 03:37:33 UTC Comment hidden (obsolete, spam)
Comment 4 QA Administrators 2023-01-04 03:19:22 UTC Comment hidden (obsolete, spam)
Comment 5 Justin L 2023-05-18 13:22:50 UTC
repro 7.6+
Comment 6 QA Administrators 2025-05-18 03:11:12 UTC
Dear Justin L,

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