Bug 99923 - Table: Can't set bottom border without top border after a page break
Summary: Table: Can't set bottom border without top border after a page break
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:
: 128415 131628 156382 (view as bug list)
Depends on:
Blocks: Table-Borders
  Show dependency treegraph
 
Reported: 2016-05-18 01:22 UTC by thexnecromancerx2
Modified: 2026-02-01 03:19 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thexnecromancerx2 2016-05-18 01:22:35 UTC
I inserted a table without borders that is larger than one page. I tried to set the bottom border of the first row of the second page. Automatically the top border is set, too. To reproduce:

1) Open a new Writer document
2) Insert a table with 40 rows
3) Mark the whole table and deactivate all borders
4) Mark the first row on the second page
5) Set the bottom border

Expected result:
Bottom border is set in this row

Observed result:
Bottom and top border are set in this row. It's not possible to deactivate the top border.
Comment 1 Cor Nouws 2016-05-18 07:35:07 UTC
Thanks for reporting thexnecromancerx2.
I confirm the behaviour, also in LibreOffice 3.3.0.
Comment 2 QA Administrators 2018-02-13 03:33:23 UTC Comment hidden (obsolete)
Comment 3 bugston 2018-02-13 08:05:05 UTC
Bug still present in
Version: 6.0.1.1 (x64)
Build-ID: 60bfb1526849283ce2491346ed2aa51c465abfe6
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: group
Comment 4 Roman Kuznetsov 2019-02-01 20:59:04 UTC
still repro in

Version: 6.1.4.2
Build ID: 1:6.1.4-0ubuntu0.18.10.1
CPU threads: 4; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
Locale: ru-RU (ru_RU.UTF-8); Calc: group threaded
Comment 5 Dieter 2020-03-29 05:58:28 UTC
Still present in

Version: 7.0.0.0.alpha0+ (x64)
Build ID: 5dcbd1bb557450a2d658a710c163b310c0cee157
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win; 
Locale: de-DE (de_DE); UI-Language: en-GB
Calc: CL
Comment 6 Dieter 2020-03-29 05:58:59 UTC
*** Bug 131628 has been marked as a duplicate of this bug. ***
Comment 7 QA Administrators 2022-03-30 04:04:44 UTC Comment hidden (obsolete)
Comment 8 Dieter 2022-03-30 06:24:07 UTC
Still present in

Version: 7.3.2.2 (x64) / LibreOffice Community
Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: ar-SY (de_DE); UI: en-GB
Calc: CL
Comment 9 Stéphane Guillou (stragu) 2023-11-16 21:28:00 UTC
Reproduced in:

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 5fe2bf914c251009ec4709fa8fdc45c3b53f676b
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded
Comment 10 Stéphane Guillou (stragu) 2023-11-17 06:55:23 UTC
*** Bug 128415 has been marked as a duplicate of this bug. ***
Comment 11 Buovjaga 2024-01-31 13:04:35 UTC
*** Bug 156382 has been marked as a duplicate of this bug. ***
Comment 12 QA Administrators 2026-02-01 03:19:29 UTC
Dear thexnecromancerx2,

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