Component: Autocomplete with updateOn blur

[SpeederX]

Describe the bug

When you setup the autocomplete with the updateOn: "blur" as value change event of the FormControl, the input will be updated only after the first selection happens, but the value will always have the last selected value by the user.
Due to how the event of blur is handled in the , this doesn't make it consistent with the logic.

The stackblitz is the one on the example page with virtual scroll, so I forked that one.

I add an additional comment as we found this bug during an integration of the component into our existing webapp. If you're ok with it I can provide already some insight on how we handled it and I think might work out to solve this kind of behavior. Are open contribution doable via fork + pr? ( new here )

Environment

Windows, Chrome

Reproducer

https://stackblitz.com/edit/fysj2c?file=src%2Fapp%2Fautocomplete-virtual-scroll-demo.html

Angular version

17.3.8-11

PrimeNG version

17.18.11-2

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20.11.0

Browser(s)

Chrome 131

Steps to reproduce the behavior

1. Click on the input of the autocomplete
2. Select one option
3. Suggestions will close and once again, click on the input of the autocomplete
4. Select one option

Expected behavior

When a user Select the option, the autocomplete should set the value to the form accordingly

[github-actions]

Due to PrimeNG team's busy roadmap, this issue is available for anyone to work on. Make sure to reference this issue in your pull request. ✨ Thank you for your contribution! ✨