Bug 169117 - VIEWING About groups of cells with outer borders
Summary: VIEWING About groups of cells with outer borders
Status: RESOLVED DUPLICATE of bug 143839
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
25.8.1.1 release
Hardware: ARM macOS (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-28 17:01 UTC by carlos_bgz
Modified: 2025-11-20 08:32 UTC (History)
1 user (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 carlos_bgz 2025-10-28 17:01:17 UTC
Select a rectangle of cells, open properties, and apply an outer border.

Within that rectangle:
- if cells are merged and a cell is adjacent to the right or bottom border, it is deleted.
- if merged cells attached to the right or bottom border are separated, the border is replicated in the left or top cell of the group.

I have done some testing and this only occurs with the right and bottom borders.
Comment 1 Sarah Lim 2025-11-14 11:47:09 UTC
this is reproducible in 

Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 620(Build:0)
CPU threads: 12; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_FI); UI: en-GB
Calc: threaded

and

Version: 25.8.2.2 (X86_64)
Build ID: d401f2107ccab8f924a8e2df40f573aab7605b6f
CPU threads: 12; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Raster; VCL: win
Locale: en-US (en_FI); UI: en-GB
Calc: threaded
Comment 2 carlos_bgz 2025-11-15 07:43:57 UTC
I am not sure if the following can be included in this request:
- In the hypothetical group of cells surrounded by a border
- I select to sort all the cells in the rectangle. Vertical sorting.
- At the position where the cell in the first row ends, a border also appears above it.
- I have not tried doing this with horizontal sorting.
Comment 3 Buovjaga 2025-11-18 16:33:12 UTC

*** This bug has been marked as a duplicate of bug 143839 ***
Comment 4 carlos_bgz 2025-11-20 08:24:56 UTC
I think it's a bad joke to consider a problem solved just because there was a similar one before. Especially when neither of them has been solved.
The original assumption is from 2021, and there is nothing in the messages to indicate that it has been resolved.
Comment 5 Buovjaga 2025-11-20 08:32:15 UTC
(In reply to carlos_bgz from comment #4)
> I think it's a bad joke to consider a problem solved just because there was
> a similar one before. Especially when neither of them has been solved.
> The original assumption is from 2021, and there is nothing in the messages
> to indicate that it has been resolved.

I'm not sure what you mean because the problem is NOT considered solved.