Comment 267 for bug 187313

> the patch needed to fix the problem does not need approval anymore

I think you misunderstand -- comment 176 on that bug says it doesn't need approval *to land on the 1.9.1 branch* (for Firefox 3.1 aka 3.5), since it's already marked as "blocking1.9.1+".

However, it still *does* need approval to land on 1.9.0.x (Firefox 3.0.x), and it can't get that approval until after it's landed on 1.9.1. Hopefully that'll happen soon.