Bug 99731 - UI Exit from Edit Mode stops button from acting
Summary: UI Exit from Edit Mode stops button from acting
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.1.2.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2016-05-08 17:50 UTC by Mark_T2016
Modified: 2023-05-26 05:17 UTC (History)
2 users (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 Mark_T2016 2016-05-08 17:50:32 UTC
After changing a worksheet back out of edit mode, attempt to operate the button will fail and the mouse click will only result in selecting the cell below the button.

Create a new worksheet document with a blank worksheet.

Add a button, using "View", "Toolbars", "Form Controls", select "Push Button" and draw a button outline on the worksheet. At this point the worksheet is in design mode. Disable design mode using the button on the Forms control toolbar. 

Operating the button from the mouse click shows the expected visible button action.

Save the workbook, this seems to be required to show the Edit Mode option.

Select "Edit", note that "Edit Mode" is now active. The button can be selected for editing but can not be actioned.

Select "Edit", "Edit Mode" to disable edit mode. 

The button can no longer be activated, attempt to click will select the cell in the sheet behind the button.

When in this mode it's also not possible to enable or disable design mode from the forms control toolbar, option is greyed out.

Close and re-open the workbook and the button can be activated again.

Also confirmed in 5.2.0.0.alpha1.

Possibly related to 
https://bugs.documentfoundation.org//show_bug.cgi?id=94378
Comment 1 raal 2016-05-11 07:12:11 UTC
Confirm. Version: 5.2.0.0.alpha1+; win7
Comment 2 QA Administrators 2017-05-22 13:38:57 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2019-12-03 15:01:51 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2021-12-03 04:46:58 UTC
Dear Mark_T2016,

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