The change in behavior was introduced in 2.01.13 and 2.02.04.
Added: Known issues 2.01.13 and 2.02.04
No, the patch1 release was an emergency fix for a single critical issue.
The issue discussed in this thread is fixed in the upcoming 2.01.15 and 2.02.06 releases.