Bug 159446

Summary: UX Design/Technical Writing: Collect and analyze tooltip text on fields
Product: LibreOffice Reporter: jan d <d_jan>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: UNCONFIRMED ---    
Severity: enhancement CC: heiko.tietze, hossein, mentoring, vsfoote
Priority: medium Keywords: difficultyMedium, easyHack, skillCpp
Version: 7.6.4.1 release   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 107739    

Description jan d 2024-01-30 11:33:46 UTC 
Problem: Writer offers "Fields", that is dynamically changeable text fragments that e.g. refer to a headline’s text, a page, a date etc. 
These fields can be inserted via: 
- Insert/Field
- Insert/Cross Reference

The fields usually show some information when hovered with the mouse. This can be useful to understand what the field does and what it refers to. However, these texts are currently not consistent. Some show the target, others just repeat the rendered field etc. 

There is potential to make this function more useful and to avoid mode switches to View/Field Names or other manual inspections. At the same time it is essential to keep the tooltip text short; we can't just add all info that might be useful.

The outcome of this task could be a table that has the following columns:

Field-Type |  Current Tooltip  | Suggested Tooltip | Reason for change/notes
Comment 1 jan d 2024-01-30 11:36:12 UTC 
Based on Stéphane Guillou’s comment: https://bugs.documentfoundation.org/show_bug.cgi?id=159299#c13
Comment 2 Heiko Tietze 2024-01-31 09:39:58 UTC 
Hossein, this could be a nice easyhack. Please add some code pointers.
Comment 3 jan d 2024-01-31 13:25:26 UTC 
@Heiko: Putting it into action is probably an easyhack, but I wondered if it should be treated as (potentially) two tasks, one of analysis, one of implementation which would enable to involve non-coders as well. (If someone wants to do both, also great)
Comment 4 Buovjaga 2024-01-31 13:27:15 UTC 
Reverting risky needinfo status which should not be used in this case.