-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dropdown: does not respect emitEvent false #16755
Labels
Type: Enhancement
Issue contains an enhancement related to a specific component. Additional functionality has been add
Milestone
Comments
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! ✨ |
mateuszstudentzero
added a commit
to mateuszstudentzero/primeng-zio
that referenced
this issue
Nov 22, 2024
mertsincan
pushed a commit
that referenced
this issue
Dec 6, 2024
* Create npm-grunt.yml Do ewentualnej modyfikacji w przyszłości * create an index.html file * Update index.html * Update index.html * Fix: Add ripple effect to AccordionTab header * Restore index.html * Fix: Dropdown respects emitEvent=false when setting value (#16755) * Drop uneccessary changes --------- Co-authored-by: joaanyk <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Type: Enhancement
Issue contains an enhancement related to a specific component. Additional functionality has been add
Describe the bug
Dropdown component emits value change event for it's corresponding control even so there is
![image](https://private-user-images.githubusercontent.com/3358993/386555270-08ebeafc-587f-4ade-ba81-f2645f7ba6a1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwMDg5MTYsIm5iZiI6MTczOTAwODYxNiwicGF0aCI6Ii8zMzU4OTkzLzM4NjU1NTI3MC0wOGViZWFmYy01ODdmLTRhZGUtYmE4MS1mMjY0NWY3YmE2YTEucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDhUMDk1NjU2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NmNlYjg4ZGU3ZTE4OTFhYTU1NGRkYTAyMTRkMmFhNGExZTc3MzNlYzQxNDhkM2M0MDkyYjAzNDI0YTRjYjdkZCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.Jk8gSptNH3TAFJe-hip7n1yQZLea2gk7VG81DpLheIU)
emitEvent: false
parameter when I call setValue. It happens only if control has no initial value or it's value isnull
. Not sure if other components have the same issue.It looks like conditions in
allowModelChange
method should be updated to fix this.Environment
stackblitz
Reproducer
https://stackblitz.com/edit/stackblitz-starters-7jmis4?file=src%2Fmain.ts
Angular version
18.1.0
PrimeNG version
18.0.0-beta.4
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
18.20.3
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: