Comment 3 for bug 1812973

Jamie Strandboge (jdstrand) wrote :

FYI, the approach we plan to take to address this issue was too involved for the 2.37.1 release, but it will be included in 2.37.2.