From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; m15) BuildID: 2000041805 Viewing page as it was built, scrollbar was not updating but leaving traces and I resized the window twice while the page was being built which caused the scrollbar to repaint. I clicked on "STOP" before the page was done, went to scroll down and as soon as I started to drag down on the scrollbar, an exception occurred Reproducible: Couldn't Reproduce Steps to Reproduce: 1.Have been unabled to reproduce it yet 2. 3. I have a log Dr Watson generated. I think it's too long, when I submit the Bugzilla enter page never comes up. Can I email it to someone?
You can attach the log to this bug. Click on "Create a new attachment" on this page: http://bugzilla.mozilla.org/show_bug.cgi?id=36560
Created attachment 7814 [details] Here is the log, there are 2 exceptions listed, the second one is for mozilla
Can you try a talkback-enabled mozilla build (such as): ftp://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-win32-talkback.zip and submit the talkback report with your email address entered into it, then we can dig up the stack trace from there. Update the bug report if you submit a report from one of these crashes. Thanks.
Adding crash keyword.
firstname.lastname@example.org - have you managed to reproduce this bug in a recent talkback build? Gerv
I'm quite sure the scrollbar leaving traceshas been submitted before.
I have been unable to reproduce this crash to date. The crash was not submitted for the scrollbar traces but rather the crash. The scrollbar traces were just used to describe the events that lead up to the crash.
marking worksforme as per reporter's comments
Status: UNCONFIRMED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WORKSFORME
Sorry for the spam. New QA Contact for Browser General. Thanks for your help Joseph (good luck with the new job) and welcome aboard Doron Rosenberg
QA Contact: jelwell → doronr
verified, can't dupe this on win98
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.