Join GitHub today
Target already setup when changing player options #12
I wonder if this could be a change detection or NgZone issue
thanks for raising the issue.
I think the primary issue is that the element that is called
I need to think on a stable and reliable solution for that
the problem is it gets lost, because the clone !== element.
Yep, I saw the PR, the problem there is that it uses undocumented / internal
However, it helped me a lot localizing the issue, thank you!