Comment 144 for bug 2561

Revision history for this message
In , Shai Berger (shai-platonix) wrote :

(In reply to comment #129)
> This very old bug is not a stop-ship for the security releases,

I agree,

> obviously we've
> lived with it for years. Once this has been checked in and tested on the trunk
> (Firefox 3 code) we can look at approving it for some future branch release.
>

But this attitude is quite disappointing. What everybody here wants, with asking for a "blocking" mark, is to make sure Firefox 3 (and 2.1, if there is one) includes a solution to this bug. What you basically say is -- if I understand correctly -- Nobody will be forced to solve it until it's solved.

Or am I misunderstanding?