Bug 138337 - Toolbar command Rename does not affect tooltip
Summary: Toolbar command Rename does not affect tooltip
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Toolbars-Tooltips
  Show dependency treegraph
 
Reported: 2020-11-19 13:28 UTC by VGP
Modified: 2023-08-14 03:13 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description VGP 2020-11-19 13:28:43 UTC
Description:
When you are personalizing a toolbar, if you rename a tool this action does not reflect on the tool tip. 
As the tool tip is generally what is visible to the end user, not the tool name, makes sense for the tool tip to reflect the renaming or to offer an option to also redefine the tool tip.

Steps to Reproduce:
1. Rover over a tool icon on any toolbar and take note of the tool tip when shown
2. Select to personalize the toolbar
3. Click on a tool on the ATTRIBUTED COMMAND column 
4. Click the MODIFY button and select RENAME
5. After the rename is done, rover again over the tool on the toolbar and verify that the tool tip has not changed.

Actual Results:
Tool tip does not change

Expected Results:
Tool rename should reflect on tool tip


Reproducible: Always


User Profile Reset: No



Additional Info:
Versão: 6.4.7.2
ID de compilação: 6.4.7.2-3.fc32
Threads da CPU: 4; SO: Linux 5.9; Realizador da interface: padrão; VCL: gtk3; 
Local: pt-BR (pt_BR.UTF-8); Idioma de IU: pt-BR
Calc: threaded
Comment 1 Buovjaga 2021-07-29 12:09:09 UTC
Repro

NixOS
Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: 67e47070a7580a17804adce812cc2f98bfe7b51f
CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: x11
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Comment 2 Buovjaga 2021-08-13 18:05:05 UTC
Already seen in 5.0 and 3.5, assuming inherited.
Comment 3 QA Administrators 2023-08-14 03:13:38 UTC
Dear VGP,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug