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

            Bug ID: 173474
           Summary: Backspace key fails to delete selected structure
                    blocks in Table of Contents settings
           Product: LibreOffice
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
In LibreOffice Writer, when editing the Table of Contents structure under the
Entries tab, selecting a structure block (such as E# for Chapter Number) and
pressing the Backspace key does not remove the block. The Delete key
successfully removes the selected block, but Backspace is completely
non-functional for this action.

Steps to Reproduce:
1. Open LibreOffice Writer and insert a Table of Contents (Insert > Table of
Contents and Index > Table of Contents, Index or Bibliography).
2. Right-click the generated Table of Contents and choose Edit Index.
3. Switch to the Entries tab.
4. Click on any structure block in the Structure line (e.g., E#).
5. Press the Backspace key on the keyboard.

Actual Results:
The selected structure block remains in the Structure line and is not deleted.

Expected Results:
Pressing the Backspace key should delete the selected structure block, behaving
the same way as the Delete key.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 26.8.0.3 (X86_64)
Build ID: bce0998afefdbc355585ca324285661a2170ba77
CPU threads: 12; OS: Windows 11 X86_64 (build 26200); UI render: Skia/Raster;
VCL: win
Locale: ar-DZ (ar_DZ); UI: ar-SA
Calc: CL threaded

--------------------------------------
Additionally, the visual appearance of the elements in the Structure bar (such
as #, E#, T) strongly resembles static UI tabs rather than removable control
blocks. This design creates a misleading impression that they are non-deletable
interface headers, leading to confusion for users trying to modify or remove
them. Redesigning these items into clear, interactive "tag" or "chip" elements
with a distinct visual state (or an explicit remove icon/hint) would
significantly improve clarity.

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

Reply via email to