[feature] implement a clickoutside event

[virgo79]

I think it would be very useful knowing how a user is closing a color picker.
he is clicking outside the colorpicker or he is hitting the cancel button?
I wondered if is there a way to obtain this without implementing a clickoutside event.
thank you very much in advance.

[bgrins]

Does the clickoutFiresChange option work for you? https://bgrins.github.io/spectrum/#options-clickoutFiresChange. In this case the clickout will just let the color value stay as-is, so you may not need to see the event?

[virgo79]

ClickoutFiresChange works great, but it not solve the problem. A generic clickoutside event would give more flexibility, as you can know how a user is closing the color picker and you can implement an event handler to better customize the user experience. Concerning how I'm using spectrum, it's a bit tricky because I've to force the trigger change of the input field inside the "move" callback handler. Due to this triggering I lose the value as-was before opening the color picker. A clickoutside event will give me the ability to restore a value previously stored with the open event.
Sorry for the tricky response, anyway I think could be an added value having a clickoutside event.
Thank you very much in advance!

[bgrins]

Concerning how I'm using spectrum, it's a bit tricky because I've to force the trigger change of the input field inside the "move" callback handler

It sounds like what would help is something like #173, where this would be an option (also related - #250). Getting all of these events tamed and unified has proven to be tricky.

In theory we could add an option to the hide() function to notify that the cancel button is clicked and send this along in the event, but that would add even more cases to handle for the previous issues. I can't think of a fix that won't add extra complexity off the top of my head - I think it would be preferable to tack #173, since that will resolve quite a few open and related issues, and make your use case much easier.

There are a variety of ways you could work around this for now - one would be to digging into the spectrum("container").find(".sp-cancel") and binding an event on mousedown to set a flag that this it is being clicked, then clear that flag on document mouseup.

[virgo79]

Ok, Thanks for the suggestion.I will try to find a workaround.

[virgo79]

Hey Brian,
I wish to thank you very much!
Following your suggestion, I found a good solution to my problem.