Description: 1. Select a cell 2. Select Data\Validity... 3. Set the following Criteria: * Allow: List * Unselect "Allow empty cells" * Entries: Enter the allowed values (e. g. A, B, and C) 4. Press OK 5. Enter an allowed value into the cell (e. g. A) 6. Now empty the cell (click it, press "DEL" and then "Return") Error: The empty cell is accepted (although switched off in step 3). Steps to Reproduce: (see description) Actual Results: Empty cells are allowed although they shouldn't. Expected Results: Empty cells should be rejected (just as any non-empty value that is not in the list). Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 8; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded
I'm not sure whether the behavior is expected or a mistake, but it changes depending on whether the "Error Alert" message is activated/checked. In both cases (error alert on or off), the content of the cell can be deleted without getting into edit mode (press [DEL] directly). Not limited to "List". Inherited from OOo.
The actual procedure seems correct to me. Think about what would happen when you set the validation options and the cell range still is empty. You also can skip the validation when you paste an invalid value.
You can't edit the cell content, and leave the cell empty.
Dear Lenge, 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
Bug still present in LibreOffice 25.2.5 Version: 25.2.5.2 (X86_64) / LibreOffice Community Build ID: 03d19516eb2e1dd5d4ccd751a0d6f35f35e08022 CPU threads: 8; OS: Windows 8.1 X86_64 (6.3 build 9600); UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded