Search results

This is actually a known problem that has already been addressed, and a fix will be pushed to the next public 11.40 build.  The internal case for it is 82793.  It will be mentioned as case 82793 in the changelog when the fix is pushed to a public build. 11.40 is already in the RELEASE update...