-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
rateChange fires on ngbRating when element is pristine #1282
Labels
Milestone
Comments
pkozlowski-opensource
added
component: rating
needs: investigation
type: bug
and removed
needs: investigation
labels
Feb 2, 2017
I can confirm that this is a valid bug. The root cause here is that we are not accounting for the initial change detection. The fix should consist of detecting initial CD and not propagating event in this case. |
fbasso
pushed a commit
to fbasso/ng-bootstrap
that referenced
this issue
Feb 8, 2017
fbasso
pushed a commit
to fbasso/ng-bootstrap
that referenced
this issue
Feb 8, 2017
fbasso
pushed a commit
to fbasso/ng-bootstrap
that referenced
this issue
Feb 8, 2017
fbasso
pushed a commit
to fbasso/ng-bootstrap
that referenced
this issue
Feb 8, 2017
fbasso
pushed a commit
to fbasso/ng-bootstrap
that referenced
this issue
Feb 8, 2017
fbasso
pushed a commit
to fbasso/ng-bootstrap
that referenced
this issue
Feb 9, 2017
fbasso
pushed a commit
to fbasso/ng-bootstrap
that referenced
this issue
Feb 9, 2017
fbasso
pushed a commit
to fbasso/ng-bootstrap
that referenced
this issue
Feb 9, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description:
when you using the rating the rateChange event fires when the element is still pristime
Link to minimally-working plunker that reproduces the issue:
link
Version of Angular, ng-bootstrap, and Bootstrap:
Angular: 2.4.5
ng-bootstrap: latest
Bootstrap: 4.0.0-alpha.6
The text was updated successfully, but these errors were encountered: