Bug 167126 - Setting a macro to "Error Alert" in a cell validation, you will not be able to key in
Summary: Setting a macro to "Error Alert" in a cell validation, you will not be able t...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
25.8.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: Macro Cell-Validity
  Show dependency treegraph
 
Reported: 2025-06-20 07:49 UTC by nobu
Modified: 2025-07-13 18:09 UTC (History)
3 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 nobu 2025-06-20 07:49:52 UTC
Description:
Setting a macro to "Error Alert" in a cell validation, you will not be able to key in.

Steps to Reproduce:
1. Open new Calc.
2. Select Cell [A1].
3. Insert Cell Validity. ( Menu - Data > Validity )
4. Criteria Tab :
   Allow : List
   Entities : a (for example)
5. Error Alert Tab :
   Action : Macro
   This bug does not affect whether the correct macro is set or not.
   You do not need to configure specific macros.
6. Close. ( Push OK Button )
7. In Cell [A1], "a" is displayed in the drop-down, and you can confirm that you can select correctly.
8. Insert "b" for Cell [A1].
9. Of course, the macro of the cell is not set, so the warning is displayed and the input is also rejected.
10. Move the cursor to Cell [A2] and try to enter some text in the cell.

Actual Results:
11. The cell is empty.
   You may be able to input using "Input line", but even if you confirm the input, it is not reflected in the cell.

Expected Results:
11. The cell should be fillable.


Reproducible: Always


User Profile Reset: No

Additional Info:

Not reproduced with
[2025-01-08]
Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 6700b311310a94e0de8123b307275cd553bb0d9b
CPU threads: 4; OS: Windows 10 X86_64 (build 19045); UI render: Skia/Vulkan; VCL: win
Locale: en-US (ja_JP); UI: en-US
Calc: CL threaded

Reproducible with
Version: 25.8.0.0.beta1 (X86_64) / LibreOffice Community
Build ID: 1b25e37a63c5a6f16bdcb365ed3da80ac419e6e4
CPU threads: 4; OS: Windows 10 X86_64 (build 19045); UI render: Skia/Raster; VCL: win
Locale: en-US (ja_JP); UI: en-US
Calc: CL threaded

Reproducible with
[2025-06-20]
Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 024053c0c140e1d167a0276f1885a21a160b45ac
CPU threads: 4; OS: Windows 10 X86_64 (build 19045); UI render: Skia/Raster; VCL: win
Locale: en-US (ja_JP); UI: en-US
Calc: CL threaded
Comment 1 Jessica 2025-06-20 09:02:32 UTC
I can confirm the bug in 
Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 497a4090de8a33704df4101fc078a48c4cf71101
CPU threads: 16; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: threaded
Comment 2 Saburo 2025-06-21 07:26:56 UTC
bibisected with win64-25.8
author	Pranam Lashkari
commit 72bbb0dd4a368dab2b1bd99917cd07d23a92a3f0

sc: make data validy error dialog async (invalid value error)