Hi,

for me its not a problem, in some cases its nice to have it

Version: 6.0.4.0.0+
Build ID: 4cb868abaf789afe3f2b4bc65454c21c08666a78
CPU threads: 8; OS: Linux 4.14; UI render: default; VCL: kde4; 
Locale: nl-BE (en_US.UTF-8); Calc: group

It is inconsistent in that the toolbar gets activated and deactivated by closing/opening this last Add dialog window. In addition, I do not think it can be useful because any action that you take is not persisted. Please, watch this screencast. At best, it is a low level nuisance type of bug. 

https://screencast-o-matic.com/watch/cFfnbuDGxD

Xavier disagrees with the request, so let's submit to the court of UX.

Obviously, the input is lost. So let's make the "Define Name" dialog modal (Sheet > Named Range > Define). Or is there a purpose of clicking around, Xavier?

Making the dialog modal should be a very simple easy hack.

(In reply to Heiko Tietze from comment #4)
> Obviously, the input is lost. So let's make the "Define Name" dialog modal
> (Sheet > Named Range > Define). Or is there a purpose of clicking around,
> Xavier?

As mentioned in the gerrit request the dialog has to stay modeless at least technically as modal dialogs break the cell range selector. This is a technical limitation and therefore many of the modeless dialogs in Calc that try to imitate modal dialogs need to stay modeless.

I'm removing all the easy hack keywords as this is far from an easy hack.

New Problem Identified:
- Upon double-clicking on any function in the "Functions Toolbar", the "Formula Bar" becomes enabled.
- Thereafter, clicking on the "Cancel" button on the "Formula Bar" will cause LibreOffice to crash and terminate prematurely.

Expected Results:
- The "Functions Toolbar" stays disabled.
- The "Formula Bar" stays disabled.

Reproducible: Always

Version: 7.1.0.3 (x64) / LibreOffice Community
Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c
CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: default; VCL: win
Locale: en-GB (en_US); UI: en-US
Calc: CL

Dear Emil Tanev,

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