WinNT4 build 2001011220 I guess there's another bug in navigator.js. Don't have that much time right now, but will attache testcase. I can simply reproduce this bug with the testcase. This might also be related to the cleanup of navigator.js. 1 - load testcase (make sure you have JS console active) 2 - use the link 3 - reload the attachement 4 - click on the green table cell and press enter 5 - move your mouse to different positions in the browser, and browser menu Keep looking at your JS console. (line 31/81/1148 and line 870) Sorry that I found this one. I hope this one will be fixed as quick as the other navigator 'bug', that was just amazing!
Make sure to put that testcase on your local hard drive to trigger the bug!
I see this on linux as well. Should this be DOM0 or event handling?
OS: Windows NT → All
Status: UNCONFIRMED → NEW
Component: Browser-General → DOM Level 0
Ever confirmed: true
Marking NEW under DOM 0. Sorry if thats not the right place.
It should be fixed now.
Yes, but what did fix this bug??
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WORKSFORME
Hmmm guess what, I was confusing this with bug 65228 (I just looked at the summary) and I remembed it was fixed so I just suggested this one was fixed too. I guess I did well since it does appear to be fixed, but it was not the one I thought it was! (do I make sense today? ;) So no idea about what fixed it.
You need to log in before you can comment on or make changes to this bug.