Comment 106 for bug 195698

Revision history for this message
In , HÃ¥kan W (hwaara-gmail-deactivatedaccount) wrote :

(In reply to comment #56)
> I understand from discussion on IRC that the size of this problem is too
> invasive on the back end to fix this close to release, so nominating for
> 1.9.0.1 instead of 1.9

Did you mean to nominate this for 1.9.1 (or whatever FF.next will be based on)? I doubt this would be accepted in a security release, if the changes would be invasive...