The color picker in Firefox sends onchange event only when it's closed. Chrome's color picker, on the other hand, sends onchange event for every color change, so we receive a bit too many if the user is moving the mouse around the picker. It would be good to not produce so many onchange events somehow.
Maybe this won't be so necessary if #3 is implemented. With clustering in place, associative memory won't be polluted too much and episodic memory should have a rate limit, which will make everything ok.
The color picker in Firefox sends
onchange
event only when it's closed. Chrome's color picker, on the other hand, sendsonchange
event for every color change, so we receive a bit too many if the user is moving the mouse around the picker. It would be good to not produce so manyonchange
events somehow.