Closing the calendar fires both onOpen and onClose events. (MUI 5)

[kenlyon]

Closing the calendar fires both onOpen and onClose events. (MUI 5)

[LukasTy]

Hello @kenlyon
I'm sorry to hear that you are experiencing this problem, but it does not seem like a critical issue.
As per our policy, the v5 is out of the support window (and even while v6 was stable, the v5 support policy encapsulates critical and security issues only).

Besides, it seems quite easy to avoid this problem by using a controlled open state. 😉

I'm closing this issue, please consider upgrading in the future to benefit from various bugfixes, improvements and new components. 👍

[github-actions]

⚠️ This issue has been closed.
If you have a similar problem, please open a new issue and provide details about your specific problem.
If you can provide additional information related to this topic that could help future readers, please feel free to leave a comment.

How did we do @kenlyon?
Your experience with our support team matters to us. If you have a moment, please share your thoughts through our brief survey.

[kenlyon]

@LukasTy Thanks for the info. I had thought it'd be likely we need to upgrade.

Just so you know, though, using a controlled open state didn't help. In fact, the first place I saw the issue, I was setting open based on a state property. It might vary, but in my case my code in the onOpen handler was causing some kind of re-render that was preventing the subsequent onClose from being received. The symptom was that the calendar was stuck open.

I mention that just in case anyone else was experiencing the same and wondering if it was just them. Either way, I'll plan to upgrade.