This issue works as intended.
Can confirm, still affects 1.16.20 and 1.16.100.51, and also change the reporter to some helper or great bug reporters, like bugsbugsbugs.
This issue works as intended.