Bug 145262 - UI: Context menu for table content with Index / Bibliography entry is missing commands
Summary: UI: Context menu for table content with Index / Bibliography entry is missing...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
Keywords: difficultyBeginner, easyHack, skillDesign, topicUI
Depends on:
Blocks: Context-Menu
  Show dependency treegraph
Reported: 2021-10-21 18:56 UTC by phv
Modified: 2021-11-10 13:40 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:
Regression By:

Testcase with index entries inside the table (13.17 KB, application/vnd.oasis.opendocument.text)
2021-11-09 17:44 UTC, phv

Note You need to log in before you can comment on or make changes to this bug.
Description phv 2021-10-21 18:56:52 UTC
By default, the commands "Index Entry..." and "Bibliography Entry..." are missing from the context menu when right-clicking an item written inside a table.

Steps to Reproduce:
1. Create a table in Writer.
2. Insert a text inside the table as "Index Entry" or "Bibliography Entry".
3. Do a right-click on the previous text to display the context menu.

Actual Results:
The context menu has no "Index Entry..." or "Bibliography Entry..." commands.

Expected Results:
The context menu should propose "Index Entry..." and "Bibliography Entry..." commands.

Reproducible: Always

User Profile Reset: Yes

Additional Info:
An easy workaround is, for the user, to customize the Table context menu, but I think that these commands may have been forgotten because the behaviour is inconsistent.
Comment 1 Dieter 2021-11-09 06:43:22 UTC
As far as I can see, there are two different context menus

a) Cursor inside the word: context menu has entry "Index Entry..."
b) Highlighted word: context menu without entry "Index Entry..."

Expected result
"Index Entry..." also in context menu of a highlighted word (either greyed out like "Cut" and "Copy" in context menu of case a) or - of course the better solution - as selectable entry

cc: Design-Team for further input and decision
Comment 2 Heiko Tietze 2021-11-09 13:11:24 UTC
Please share a short example document.
Comment 3 phv 2021-11-09 17:44:50 UTC
Created attachment 176169 [details]
Testcase with index entries inside the table

Here is a testcase: The index entries are in a table, but the relative commands are not listed in the "Table" context menu. Same issue for bibliography entries.

Just as the hyperlink commands are always available for the contents of a table, the commands for index and bibliography entries should be proposed.
Comment 4 QA Administrators 2021-11-10 04:09:19 UTC Comment hidden (obsolete)
Comment 5 Heiko Tietze 2021-11-10 07:47:27 UTC
The command .uno:IndexEntryDialog needs to be added to /core/*/uiconfig/*/popupmenu/table.xml

But I wonder if we really need to provide every interaction at the context menus. The table menu is large right now, having indices in tables is not a common use case (neither to edit from there), and the command is easy to customize. OTOH, it wont be shown in the menu unless an index is clicked. What actually bothers me is the user expectation to have everything at hand. Do we comply?

(In reply to Dieter from comment #1)
> Cursor inside the word... vs. Highlighted word...

The command is hidden on multi-selection, whether within a table or ordinary paragraphs. Probably to ensure it's a single entry without checking boundaries. Different topic anyway.
Comment 6 phv 2021-11-10 12:39:49 UTC
Hence my initial questioning - is this issue an oversight or a purposeful omission? - that made me hesitate between a minor bug report or an enhancement request.

What qualifies commands to appear in the "Table" contextual menu because there are commands for hyperlinks, and indexes inside table but none for the index and bibliography entries. Is the last instance less common than the second one?

It's the lack of coherence in the contextual menu for the same element outside the table and in a table that bothers me the most: I expected to reproduce the same behavior with the right-click, no matter where the entry is.

The concern may be minor and easily overcome; but it brings up some considerations without challenging the expertise of the UI/design team.
Comment 7 Heiko Tietze 2021-11-10 13:40:40 UTC
(In reply to phv from comment #6)
> It's the lack of coherence in the contextual menu for the same element
> outside the table and in a table that bothers me the most...

Convincing argument. Let's add the command to the table menu. 

Code pointer in comment 5.