Yes, it was fixed with the next hotfix: Release 3.11.1
Make sure that you are always working with the latest release.