ID 539658 - setChangedScript() is not triggered by updating the value of custom Color preferences

Problem summary
setChangedScript() is not triggered by updating the value of custom Color preferences. 
 
Customer reported version
Mari 6.0v1
 
Customer reported platform
Windows 10
 
Steps to reproduce
 
1) Open Mari.
 
2) Open the Python Console and run the following code:

import maridef changeScript():	print('Pref changed')color = mari.Color(0,0,0,1)mari.prefs.set("Node Graph/Test/TestColor",color)mari.prefs.set("Node Graph/Test/TestFloat",1.0)mari.prefs.setChangedScript("Node Graph/Test/TestColor","changeScript()")mari.prefs.setChangedScript("Node Graph/Test/TestFloat","changeScript()")

 
3) Navigate to Edit > Preferences > Node Graph and find the custom preferences added by the Python code:
 

 
4) Change the value of Test Float and notice that Pref Changed is printed to the Python Console. 
 
5) Change the value of Test Color and notice that nothing is printed to the Python Console.
 
Expected behaviour
The setChangedScript() function should be triggered when updating custom Color preferences.
 
Actual behaviour
setChangedScript() is not triggered by updating the value of custom Color preferences. 
 
Workaround
Unknown.
 
Reproduced by support
This bug has been reproduced in:
Mari 6.0v2 - Windows 10 - Linux CentOS 7
Mari 5.0v1 - Windows 10 - Linux CentOS 7
Mari 4.2v1 - Windows 10 - Linux CentOS 7
 
Earliest version tested
Mari 4.2v1
- This issue appears to be in all tested versions of the product