Comment 20 for bug 1532264

Thanks for explaining the larger problem here. It's a bit frustrating that this bug has existed for more than 9 years, (it seems the original fix was put in in 2011), but it's taken this long to finally swat it.

Sounds like we're finally on the right path to getting this fixed. Thanks again.