Hi Mark,
Sorry for the inconvenience caused. We are changing the control architecture to fix this problem, due to this complexity we have not moved the fix in our Vol 1 SP 1 release. The reported issue has been fixed and the fix will be available in our upcoming weekly NuGet release, which will be available on May 21st, 2019.
Thanks,
Muneesh Kumar G.