Thanks for acknowledging the report.
If you’ve replicated the issue, is a fix planned for inclusion in next patch release?
