Created attachment 151721 [details] Calc "format cells" does not leave background "as is" When you select a range of cells with, for example, various fonts, and you change a different attribute - for example, the background - LibO Calc leaves all the different fonts "as is." However, if you (1) change the background on a cell, and then immediately (2) select another range of cells with various backgrounds, and change a different attribute - for example, the font - LibO Calc also changes all the selected cells' backgrounds to "none."
I can not confirm with Version: 6.3.0.0.alpha1+ Build ID: 53325b40b557cc84d8d21c1baa0ef8d3bfc00ab8 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Can you confirm with Version 6.2.3.2 on macOS 10.14.5, or on other hardware and OS? Also, it is important that after you (Step 1) change a cell's background, you IMMEDIATELY (Step 2) select a range of cells with different backgrounds. Then, when you select Format>Cells, the Background panel will be selected, with None highlighted. If you change to another format panel and change an attribute, the cells' backgrounds will also be changed to None. A workaround is to select the range in Step 2, Format>Cells, select another format panel (e.g., Borders), and click Cancel. Then when you Format>Cells again, the Borders panel will come up. You can change borders without changing backgrounds.
I only see this : - in the first cell of the selected block after font or border change, and - only the first time that a cell from the block is inspected via right mouse button click Format cell entry. Note that visually, the colours are always displayed, irrespective of what the properties dialog shows. Any further or subsequent display of the property of the cell shows the correct background colour in the corresponding attributes tab. Tested with Version: 6.4.0.0.alpha0+ Build ID: eda0568ec550a10b962c2427edfe05ea3197f107 CPU threads: 4; OS: Mac OS X 10.14.5; UI render: default; VCL: osx; Locale: fr-FR (fr_FR.UTF-8); UI-Language: en-US Calc: threaded
Confirming, but only in line with my comments.
Created attachment 152200 [details] Video of Bug 125541 This video demonstrates Bug 125541.
Created attachment 152203 [details] Bug 125541 does not happen in OpenOffice The same steps do not produce Bug 125541 in Apache OpenOffice 4.1.6.
Dear peterpqa, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
no repro in Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 18771471f75685a6d3838a22d16dcff5c398e652 CPU threads: 4; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: ru-RU (ru_RU.UTF-8); UI: en-US Calc: threaded petrpqa, could you retest your problem in latest stable 7.1.5 version or in 7.2.0.3 or in current master build (future 7.3 release)?
Dear peterpqa, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear peterpqa, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp