I submitted a new idea this morning for a problem we first reported way back in 2013:
This problem was supposed to have been fixed in v10.1, but a quick test today revealed that it remains in v12.3.6.