Bug 67959 - UI: Provide way to remove cross-references, once set (other then copy&pasting as unformatted text)
Summary: UI: Provide way to remove cross-references, once set (other then copy&pasting...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Blocks: Fields-Cross-Reference
  Show dependency treegraph
Reported: 2013-08-09 20:37 UTC by sergio.callegari
Modified: 2019-02-05 18:49 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description sergio.callegari 2013-08-09 20:37:59 UTC
Problem description: 

when you set a reference over "Insert - Fields - References - Set
reference", there is no easy way to delete this reference afterwards.
The only way to do this is to select the text where the reference has been set, cut and paste as unformatted text.

Steps to reproduce:
1. Select a piece of text
2. Insert->Cross Reference->Set Reference + give a name to the reference, say 'xxx'
3. Try to get rid of that reference since you realize that you do not need it and you want to keep the cross-reference space tidy

Current behavior:

You cannot do that

Expected behavior:

There should be a way to remove the cross reference, for instance, from the navigator by selecting the reference and pressing del or from the cross reference panel with a 'delete reference' entry.

This bug has been open since version 1.1.3 of openoffice.org. See https://issues.apache.org/ooo/show_bug.cgi?id=35292
Operating System: All
Version: release
Comment 1 Cor Nouws 2013-08-09 22:17:30 UTC
Hi Sergio,

Intersting problem. Thanks for the report and the suggestions to solve.

I mark it as New & Enhancement & version 3.3.0 (olderst LibreOffice)

Comment 2 Gilvan Vilarim 2014-05-18 17:25:38 UTC
Confirmed on LO 4.2.4. Is is really hard do delete a reference.

Changed version because the situation persists in all LO versions.

Comment 3 Dieter 2017-06-04 12:29:30 UTC
Still present in LO 5.3.3
Comment 4 Xisco Faulí 2017-06-12 10:56:38 UTC
Changing version back to the earliest version affected.