Hi,
I can confirm that this bug still exists in 5.2.2. I migrated an application from 4.x to 5.2.2 today.
I will try to provide a TestCase in a few days.

Regards
Matthias