Still an issue in 1.20.2
Affects 1.18.2 hotfix
Can confirm this bug exists in 1.17.10.
This issue has reappeared in 1.17.10.
Still an issue in 1.20.2