This issue has been reported to the product team and will be fixed in a future release.
See previous report: