I’ve also had other issues with the “show colors” pop-up. I’m not writing “This is exactly how to replicate it steps” here, but basically I’ve had several occasions where it stops working (I select a colour and it doesn’t change what I was trying to change) I think it’s due to me clicking on the text again once the dialogue is open.
For example I pasted in a couple of tables earlier and wanted to set the border colour. It worked once, but without closing the table or colour picker dialogues it then started changing the colour of the text and not the border (I was trying to find a “just-visible” grey).
Basically I think the colour picker can forget what it is you’re trying to change.
The OS X colour picker is notoriously tricky. I sends its messages to the first responder, but all sorts of things can mess it up, because it’s hard-wired in so many odd ways, so it can cause issues wherever it’s used. If you can find a particular reproduction case, though, let me know, as I haven’t seen this and can’t reproduce it off-the-bat.
Both of these instances describe expected behaviour. The comment pane must be first responder for the colour panel messages to get sent to it. In both of these examples, you click into the editor, so the editor takes first responder status at that point. From there on, colour panel messages will be sent to the text, which will generally affect text foreground colour. That’s not a bug, but how the entire Cocoa view system is set up - each view can use the colour panel in a different way.