Description: with the to-be-attached document, the second (bar) chart contains a cell reference range for the border-color property of the first data series, and it refuses to allow me to unset it. if you remove it and clock 'okay', then come back, it's just restored it. is this correct behaviour or a bug? note that i'm experiencing multiple issue with this document, most significantly as documented in bug #135822. 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
Created attachment 164365 [details] the mentioned document
Thank you for reporting the bug. Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. Please provide a clearer set of step-by-step instructions on how to reproduce the problem. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the steps are provided
To reproduce: 1. Open the attached document. 2. Click 'edit' to enable editing. 3. Click on the second chart (bar graph) in the first sheet ("current"). 4. Open the 'edit data ranges' dialog. 5. Select the 'data series' tab. 6. Select the 'border colour' data range for the first data series ('small'). 7. Delete the contents of the range textbox. 8. Click 'ok'. 9. Repeat steps 3-6 as necessary, to thus notice that the range has been restored since you tried to delete it, as though the change was not saved. Alternatively to steps 8-9 you can just select a different data series then go back to 'small' to see the text deleted in step 7 has been restored.
Repro with document 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
The range is not yet visible in the oldest of Linux 43max repo and the problem is seen already in the latest of 43max
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