One of the users marked it as Fix Released. The bug attached to the
report is not on the official list of fixes for 3.0.11, but users report
the issue is gone.
John Vivirito wrote:
> On 07/02/2009 09:59 PM, Bananabob wrote:
>
>> I have been asked by email to comment on this bug. I now have Firefox
>> 3.0.11 and it appears to be fixed for me. Thank you
>>
>>
> Upstream was going to add this to .10 however .10 ended up being a major
> regression fix so they planed on .11 it says this early in the bug. Has
> no one marked this as fixed released yet?
>
>
One of the users marked it as Fix Released. The bug attached to the
report is not on the official list of fixes for 3.0.11, but users report
the issue is gone.
John Vivirito wrote:
> On 07/02/2009 09:59 PM, Bananabob wrote:
>
>> I have been asked by email to comment on this bug. I now have Firefox
>> 3.0.11 and it appears to be fixed for me. Thank you
>>
>>
> Upstream was going to add this to .10 however .10 ended up being a major
> regression fix so they planed on .11 it says this early in the bug. Has
> no one marked this as fixed released yet?
>
>