This bug has been all fixed up and released today in 8.16.0.5248. If you find that the fix is not in place and are still on 8.16.0.5234, you are one of a handful of sites that will receive the fix tomorrow.
Thank you for your patience during that pain point!
Cheers,
Beth