Found this issue’s title funny, and I appreciate the last dev’s honest reply:

Thanks for the follow-up, and I’m sorry this issue was left unresolved for so long.

I took another look at it, and the problem has now been fixed, and the fix will be available in 2026.3 and 2026.2.3 :)

Unfortunately, with a large number of issues in the tracker, some older reports can remain under the radar much longer than they should. I understand how frustrating that can be, especially after waiting for years.

Thank you for reporting the issue and for providing a reproducible case — it was still valuable in getting this fixed.