Neil wrote:
Jan Gundtofte-Bruun wrote:
Neil wrote:
Jan Gundtofte-Bruun wrote:
Heh, thanks. Cool you've registered it for me.
And I've fixed it for you.
...or have you? Hmm.
With the Mozilla v1.4 browser running under Windows XP, I was still able to recreate this bug. I don't know what happened to Neil's checkin but to me it seems to me that the fix somehow missed the target.
target? Nobody targetted it, did they?
"Target" was not meant to be used as a technical word (apparently), but rather that I'm still seeing the issue after the fix has been applied.
Well the fix hit mozilla after 1.4 was released...
As it's only a JavaScript fix you could use PatchMaker to apply it to your 1.4
Err, sorry -- I'm not a coder. I think I'd better not PatchMakerize that fix into my local installation. I'll just live with it as it is.
Although I've yet to upgrade to 1.4 myself; now that I've got cable I can afford to upgrade and I'll be adding in some of my personal enhancements - perhaps I could create a download that would apply those enhancements to your 1.4 installation too.
