Is this issue fixed in Sharepoint 2016?

Feb 15, 2017 at 10:26 AM
Hello,

Could anyone tell if this issue is already taken care by Microsoft in Sharepoint 2016 version?


Thanks,
Mayuri