MuliSelect | throws error when double clicking on trigger icon
**Reproduction: ** double click on trigger icon
https://stackblitz.com/edit/dtvhna-mlyhdq?file=src%2Fapp%2Fdemo%2Fmulti-select-virtual-scroll-demo.htmlthrows error when double clicking on selection container
This bug looks like it's related: https://github.com/primefaces/primeng/issues/12778
@cetincakiroglu - any luck resolving this issue? I see it was removed from 16.6.0 milestone. Thanks!
This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!
This is still an issue for us. We're currently using 16.02 - I haven't tried 17 yet, but I assume it's still an issue in the latest version.
This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!
This is still an issue. Do not close
On Thu, Jun 27, 2024, 18:02 github-actions[bot] @.***> wrote:
This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!
— Reply to this email directly, view it on GitHub https://github.com/primefaces/primeng/issues/13808#issuecomment-2195904225, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAKFRT5QS7UUGCR67SXUH3ZJSY23AVCNFSM6AAAAAA5TXCQEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJVHEYDIMRSGU . You are receiving this because you are subscribed to this thread.Message ID: @.***>
This is still an issue.
This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you for your understanding!