Yes, this issue has been fixed in the latest update. From my testing, I am no longer experiencing the issue, and from what you describe it seems like you aren’t experiencing the issue either.
Sorry for the confusion. There were many fixes and new features for this update and it looks like we missed this in the release notes.
