It has indeed been fixed, but there is some question as to whether the content made it into the nightly. There was an expedited release yesterday (8.1.35, which contained only one important fix which was a problem in 8.1.34), and our release mechanisms might not have caught up. It will absolutely be part of the 8.1.36 release.