Bug 103219 - DIALOG: Renaming image name to an existing name should prompt user
Summary: DIALOG: Renaming image name to an existing name should prompt user
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Image-Dialog
  Show dependency treegraph
 
Reported: 2016-10-14 16:57 UTC by Harald Koester
Modified: 2024-02-05 03:12 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 Harald Koester 2016-10-14 16:57:40 UTC
Steps to reproduce:
[1] Create new text document and insert 2 images.
[2] Open Navigator. Two images with names 'Image1' and 'Image2' are displayed.
[3] Working area: Right click on 'Image1' > Properties… > Tab 'Options'
[4] Insert new name, then OK. Name is changed to new name in Navigator.
[5] Working area: Right click on 'Image2' > Properties… > Tab 'Options'
[6] Insert same name as in step 4, then OK. Name changes from 'Image2' to 'Image1' in Navigator. Expected: Either error message, that name already exists or button 'OK' should be greyed, when same name is inserted (equal if you rename image in Navigator).

Used version: 5.2.2.2 release.

Bug already exists in version 3.3.0 with slight differences of the user interface. Hence inherited from OOo.
Comment 1 Yousuf Philips (jay) (retired) 2016-10-17 05:56:49 UTC
Hi Harald,

Thank you for reporting the bug. Confirmed.

Version: 5.3.0.0.alpha0+
Build ID: 45a7137c6796f33fbf5b8f7cb64e293260d991cb
CPU Threads: 2; OS Version: Linux 3.19; UI Render: default; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-10-13_23:38:06
Locale: en-US (en_US.UTF-8); Calc: group
Comment 2 QA Administrators 2017-10-23 14:06:12 UTC Comment hidden (obsolete)
Comment 3 Harald Koester 2017-11-11 15:42:31 UTC
Bug still exists in version 5.4.3 (64 Bit, Win7).
Comment 4 QA Administrators 2018-11-12 03:41:01 UTC Comment hidden (obsolete)
Comment 5 Harald Koester 2018-12-03 21:47:29 UTC
Bug still exists in version 6.1.3 (64 bit. Win 10).
Comment 6 QA Administrators 2019-12-04 04:21:35 UTC Comment hidden (obsolete)
Comment 7 Harald Koester 2020-02-04 12:49:28 UTC
Bug still exists in version 6.4.0 (64 bit, Win 10).
Comment 8 QA Administrators 2022-02-04 03:41:27 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2024-02-05 03:12:07 UTC
Dear Harald Koester,

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