This bug has existed since version 1.21.9, and subsequent versions 1.21.10, 1.21.11, and the current 26.1 have not fixed it.
This bug has existed since version 1.21.9, and subsequent versions 1.21.10, 1.21.11, and the current 26.1 have not fixed it.