Has anyone checked Firefox 2.0 on AMD64/edgy for this bug? I no longer have access to the AMD64 install that I was experiencing this bug on.
Has anyone checked Firefox 2.0 on AMD64/edgy for this bug? I no longer have access to the AMD64 install that I was experiencing this bug on.