https://bugs.documentfoundation.org/show_bug.cgi?id=170507

            Bug ID: 170507
           Summary: WRITER - cell frame border can not be removed after
                    row is removed
           Product: LibreOffice
           Version: 25.8.4.2 release
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
When you add a border (line) between two cells and remove one row, the line can
no longer be removed in the table settings menu.

Steps to Reproduce:
1. Add table with three lines (or use attached demo file)
2. Remove all borders of the table
3. Add a border (line) between cells of line 2 and line 3
4. Remove line 2
5. Try to remove the border (line) between line 1 and 3

Actual Results:
Line can not be removed

Expected Results:
line can be edited and removed (table can be edited is if the row wouldn't have
been deleted)


Reproducible: Always


User Profile Reset: No

Additional Info:
In my testing I couldn't reproduce the same bug with columns (so three columns
instead of rows)

1) Linux
LibreOffice:
- Version: 25.8.4.2 (X86_64) / LibreOffice Community
- Build ID: 290daaa01b999472f0c7a3890eb6a550fd74c6df
- CPU threads: 12; OS: Linux 6.14; UI render: default; VCL: gtk3
- Locale: de-AT (de_AT.UTF-8); UI: de-DE
- Flatpak
- Calc: threaded

System:
- Operating System: KDE neon User Edition
- KDE Plasma Version: 6.5.5
- KDE Frameworks Version: 6.22.0
- Qt Version: 6.10.1
- Kernel Version: 6.14.0-37-generic (64-bit)
- Graphics Platform: Wayland

2) Windows (REPO)
LibreOffice:
- Version: 24.2.6.3_AA (X86_64) / LibreOffice Community
- Build ID: 23735e228767740599e3f00b9371b05bcbf243d2
- CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
- Locale: de-AT (de_AT); UI: de-DE
- Calc: threaded

System:
- Operating System: Windows 10

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to