As of June 2026, I'm still able to reproduce this issue. I filed a bug using Feedback Assistant. The Feedback ID is FB22938104.