Blur event or property "open" is not reactive in some situations concerning auto-complete component

[GlebNekrasov]

• I have searched the issues of this repository and believe that this is not a duplicate.

Version

4.1.0

Environment

Windows 10 Home (build 19045), Google Chrome 121.0.6167.189, Vue 3.2.13

Reproduction link

Steps to reproduce

1. Input "son" at top input-field. After that dropdown will open.
2. Click anywhere out of top input-field. Dropdown will be shown yet.

What is expected?

After click out of input-field dropdown should be closed.

What is actually happening?

After click out of input-field dropdown stays opened.

---

I created component "SearchField" using auto-complete component of Antdv. At SearchField template I bound option "open" to reactive variable "isDropdownActive". This variable is changed by 4 events: change, select, focus and blur. Events change and select work correctly. As for blur event, it changes "isDropdownActive" value correctly (you can see it at console), but changed value of "isDropdownActive" doesn't effect on dropdown status. Perhaps, reactivity is destructed somewhere in this sequence.

[aShu-guo]

the usage of ref is incorrect, you should use .value to modify the value. for example

const changeHandler = (value) => {
  isDropdownActive.value = value.length >= props.minLengthDropdown;
  console.log("changeHandler");
  console.log("value length = " + value.length);
  console.log("isDropdownActive = " + isDropdownActive);
};

codesandbox

[GlebNekrasov]

the usage of ref is incorrect, you should use .value to modify the value. for example

const changeHandler = (value) => {
  isDropdownActive.value = value.length >= props.minLengthDropdown;
  console.log("changeHandler");
  console.log("value length = " + value.length);
  console.log("isDropdownActive = " + isDropdownActive);
};

codesandbox

It's the shame mistake on my side. Now all work correctly. Thanks a lot.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.