Ran headfirst into this issue earlier this week. Unfortunately, the issue was not fixed in 1.4 as of Monday.

Judging by their published release timeline, 1.4 is set to be released the first week of March, I dont think a fix will make it in to 1.4. :[