I believe this has been fixed with bug 1435283 which is in the proposed 1.24.7. Could you test with that level to verify that it has been resolved?
I believe this has been fixed with bug 1435283 which is in the proposed 1.24.7. Could you test with that level to verify that it has been resolved?