Bug 135817 - closing chart data editing dialog blocked by another
Summary: closing chart data editing dialog blocked by another
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Chart
  Show dependency treegraph
 
Reported: 2020-08-17 00:06 UTC by Lyndon Brown
Modified: 2023-04-09 03:26 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 Lyndon Brown 2020-08-17 00:06:55 UTC
Description:
if you open the data editing dialog for a chart in one document, then switch to another document and do the same, you cannot close the dialog of the first, via 'close', 'okay', or 'x', until you do so with the second, or rather the action seems to get queued and executed only on close of the last opened one.

similarly if you click on 'help', this is also only executed later upon closing the last opened dialog.

Actual Results:
 

Expected Results:
 


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 7.0.1.1.0+
Build ID: <buildversion>
CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.utf8); UI: en-GB
Debian package version: 1:7.0.1_rc1-1
Calc: threaded
Comment 1 Buovjaga 2021-04-08 15:42:39 UTC
I repro on Windows and all Linux VCL backends except kf5. The dialog I used was Data Ranges. Already seen with version 3.3.0 on Win 10.

The dialog is modal.

Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 7d6e12c01e6c1dd050818a2ea76faa6bf89e41f1
CPU threads: 2; OS: Windows 10.0 Build 19042; UI render: default; VCL: win
Locale: fi-FI (fi_FI); UI: fi-FI
Calc: threaded
Comment 2 QA Administrators 2023-04-09 03:26:18 UTC
Dear Lyndon Brown,

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