The description of fixed issue 1110117 says "This issue is expected to be resolved in a future release." which doesn't make sense for a fixed issue. The description hasn't been reworded since it was a known issue. It should be reworded to reflect that this is now fixed.
Verified in release notes 6.4.0-12