Fix this would be very appreciated.

.off can be chained with .on

Also I guess stopPropagation, stopImmediatePropagation and preventDefault are the right solution.

Hi @DanielRuf
Thanks for your response.

I think chaining off and on would end up adding the event listener back too early, in the same cycle, while the event is still alive. That is why there is a setTimeout between them.

And I think this solution may be less intrusive than stopping the propagation of the event, as the event could still be used by other parts of an application. Probably an important consideration for a library.

Please have in mind that this PR is more than three years old, and I am talking from memory here. Don't take my word without running tests yourself ;)

Merging for now but may need some small changes.

@DanielRuf this merge seems to give me an error:
ReferenceError: Can't find variable: focusToOpen

If the input is in a label the picker can't be closed, if a container is specified the error still occurs though it will close as expected.

Ah I see. Missed that. I guess it should be handleFocusToOpenEvent?

Yeah. That kills the error but doesn't allow an input to work inside a label.

I see the problem actually:
$ELEMENT.off('click.' + STATE.id)
Should be
$ELEMENT.off('.' + STATE.id)
That seems to work correctly in my quick test.

Along with:
$ELEMENT.on('click.' + STATE.id, focusToOpen)
Should be:
$ELEMENT.on('click.' + STATE.id, handleFocusToOpenEvent)

Do you want to provide a PR? That would be very helpful.