We are planning the 5.3.1 release tomorrow, so if you are able to get a test case first thing in the morning, we might be able to see about getting this fixed in 5.3.1.