Skip to content
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

Changing value via [colorPicker] should not cause a (colorPickerChange) event to fire. #18

Closed
ImAllInNow opened this issue Aug 18, 2016 · 0 comments

Comments

@ImAllInNow
Copy link

We are attempting to use this color picker to choose the color of a ui element in our system. We have an undo/redo system to allow users to undo changes they make. We listen for (colorPickerChange) to add items to our undo/redo stack. When a change is undone, the color of the ui element changes which is passed to the color picker via [colorPicker]. But this in turn causes another (colorPickerChange) event to fire. This results in committing a new item to the stack when there shouldn't be one.

similar to this issue with md-checkbox: angular/components#820

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant