This is an issue with the 1.8 branch (FF2) but has been fixed in Firefox-3.0. It looks like they are looking into it to fix it but we have to wait for upstream to drop a fix and we will carry it over from upstream.
This is an issue with the 1.8 branch (FF2) but has been fixed in Firefox-3.0. It looks like they are looking into it to fix it but we have to wait for upstream to drop a fix and we will carry it over from upstream.