Take a basic angular-color-picker setup and simply add the ngMaterial module to your app and this conflict will present itself. No material elements in use, just add the module to the app.
Every time you open the picker, the color picker picker will be reset to 0, 0 even though the model still represents the expected color. You can select a new color but next time you open the picker it will be back to 0, 0.
This also means that the onChange will not fire if you want to go from a color to white since white is 0, 0.
Take a basic angular-color-picker setup and simply add the ngMaterial module to your app and this conflict will present itself. No material elements in use, just add the module to the app.
Every time you open the picker, the color picker picker will be reset to 0, 0 even though the model still represents the expected color. You can select a new color but next time you open the picker it will be back to 0, 0.
This also means that the onChange will not fire if you want to go from a color to white since white is 0, 0.
Example: https://embed.plnkr.co/5WhF3yzX2Wbin4g6Q7Hg/