mozilla bug 128153 was not the right one ... updating remote bug info for this.
BTW, this should be fixed in firefox 2.0.0.x. Can anyone with edgy/feisty confirm that this is gone?
mozilla bug 128153 was not the right one ... updating remote bug info for this.
BTW, this should be fixed in firefox 2.0.0.x. Can anyone with edgy/feisty confirm that this is gone?