I just downloaded 15.23.1, and like you, I hope it solves the problem.
Unfortunately, there are no new release notes for this version. Perhaps that's because it's only available for people who opt-in to Office Insider updates.
Still, if a new release is supposed to fix a bug, shouldn't the release notes say so? If the release notes said this bug is supposed to be fixed, I'd be glad to post a note confirming that. (Or letting them know that I still have the problem.) That's probably
more important for people running pre-release software. After all, if they've changed code in an attempt to fix this bug, wouldn't they want feedback from users to know if it worked, or if it still needs tweaking?
If there aren't any release notes, then I don't what bugs I should be testing for.
And if this release does not include code changes to fix this bug, then I don't want to waste my time reporting that the bug's still there when (presumably) they know it's still there, because they haven't yet released a fix.
Microsoft, to release early versions without release notes is disrespectful to your users. I want a better products, and I'm happy to contribute my time reporting issues and testing fixes. I'm not happy to have my time wasted reporting what you already
know, but haven't publicly acknowledged.