Just to confirm, we do indeed believe this issue is fixed in our internal builds and the fix will be included in the next major version.
Just to confirm, we do indeed believe this issue is fixed in our internal builds and the fix will be included in the next major version.