Thanks for the support Jason, looking forward to have this issue fixed.

Yes, the bug report number is FB11723920