This issue was supposedly fixed back in 12.2. Sounds like it was either unintentionally reverted, or never fixed to begin with.
This issue was supposedly fixed back in 12.2. Sounds like it was either unintentionally reverted, or never fixed to begin with.