Can confirm this is also happening again in 5.3.2 after it was previously fixed. Also the workaround that I posted for the original bug no longer appears to be working. I have submitted another bug report.
1 Like