From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.0.0) Gecko/20020529 BuildID: 2002052917 Three different occasions with same effect. Once, using open web location, inadvertantly put in a URL site with ".com.com" at the end. Dialogue box came up saying could not find site. Pressed "Okay" and button clicked, but dialogue box would not go away. clecking anywhere brought an error tone. Force quit reported that I would be force quitting the N0650 Buttom Manager. Machine froze once force quit was chosen Second Time, trying differing combinations of http://www.verizonrebates.com. Same dialogue box - this time it worked correctly several times before jamming. Same message re: N0650 Button Manager. same result Third time, a window asking approval for a cookie came up. Pressed the okay and had the same series of problems. Reproducible: Sometimes Steps to Reproduce: 1From file menu open web Location 2.input an http://www.pickasite.com.com 3.When dialogue box comes up reporting no such site, press "okay" Actual Results: dialogue box remains on screen. cannot move to any other window. Main Menu may drop down, but no choice will be activated. Expected Results: Dialogue box should have closed, returning to previously-opened browser window, allowing you to continu See desciption above.
WorksForMe using Mac/2002080208/9.2.2. Gary, can you still reproduce this problem using a current build? If so, does Mozilla generate TalkBack reports following these abnormal quits?
Summary: crash on button dialogue box → Hang on button dialogue box
no answer -> wfm
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME
The problem persists in the new 1.1 build. No talkback messages get generated from this activity. I have to work through a series of Force Quits before I get to the Mozilla force quit; First for the N122U button Manager, then the N065U button Manager, then the printer's printmonitor and finally the Mozilla force Quit. The machine only locks up at the mozilla force quit; the others respond.
You need to log in before you can comment on or make changes to this bug.