Closed
Bug 178316
Opened 22 years ago
Closed 21 years ago
Composer hangs Mozilla when I click on "Open" or "New" buttons on Mac OS X
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: meyers, Unassigned)
Details
(Keywords: hang)
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2b) Gecko/20021016 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2b) Gecko/20021016 When I try to open file through composer using the New or Open buttons or menu items, Mozilla stops responding and I have to Force-Quit it. I can only open files by finding them in the browser and using the Edit Page menu item. Reproducible: Always Steps to Reproduce: 1. Open Composer 2. Click on the "Open" button 3. Force-Quit Mozilla Actual Results: Mozilla stops responding, shows up as red in the list of processes in the Force-Quit window, and needs to be killed. Expected Results: Mozilla should have presented the open file dialog, and later open the file chosen . This worked in version 1.1
WorksForMe using FizzillaCFM/2002103011 on 10.1.5. Rob, please retest using a recent nightly build.
Keywords: hang
Summary: composer hangs mozilla when I click on "Open" or "New" buttons on Max OSX → Composer hangs Mozilla when I click on "Open" or "New" buttons on Mac OS X
can you attach the file you are trying to open? worksforme isn't convincing until we have a stab at the content. If you can't share the content, can it be simplified or prepared in such a way that it still causes the problem but doesn't share any information you would rather not share?
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Reporter | ||
Comment 3•22 years ago
|
||
I think I figured out what it is. When I'm at work, I have a network drive mapped from my powerbook to my unix home directory at work. Later, when I'm at home and can't have that drive mapped, when I try to use Composer (or save files sometimes) I think Mozilla is trying to access the mapped drive for whatever reason and is blocking on that.
Comment 4•22 years ago
|
||
Rob Meyers--Can you please retest with a newer build. There were lots of key changes that happened in Composer in early November which may have fixed this or made it worse. I don't see a problem with Open or New icons in my macho OSX build.
Assignee: syd → composer
Status: ASSIGNED → NEW
tested with trunk. WFM.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•