ShadowDOM Support Broken about mcdatepicker HOT 5 OPEN

Hi,

This change was made because MCDatepicker uses one calendar node for all calendar instances.

Before this commit, the calendar node was added only to the context of the first instance.

For example: if you have 2 instances, the first one using document.body as context and the second one shadow root,
in this case, MCDatepicker will append the calendar node only to the document.body (the context of the first instance). The second instance will use its context just to search the node with the id specified in the el option and add a listener to it.

from mcdatepicker.

I see. In order to fully support shadow dom the element would need to be inserted there.

Perhaps the package can be modified so that a date picker is inserted into each context? That way you maintain support for multiple pickers while also supporting shadow dom.

from mcdatepicker.

Yes, I think it's a good idea!

from mcdatepicker.

Hi @mikecoj any update about this shadow dom support?
This issue can be fixed adding one more options to append the picker to the given Element.
Ex: appendTo : shadowEle

from mcdatepicker.

Hi there,
unfortunately, there are no updates on this.

Due to my involvement in other big projects, I had to dedicate more time to them and less time to this one. I hope this will change soon.

If you've found the solution, I'll be happy to receive a PR from you.

Thank you!

from mcdatepicker.