Closed
Bug 276926
Opened 20 years ago
Closed 19 years ago
Windows Fail to Open and Render
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: redunn, Assigned: bugzilla)
Details
Windows 2000 Pro, workhorse of a machine running everything from Thunderbird 1.0 and Mozilla 1.7.1 to MySQL and IIS and Diablo II. Installed Firefox 1.0 over 0.9.3. Extensions seemed to update fine (those it could - others disabled) and install went swimmingly. First window presented would not render any content nore would it show my personal toolbar bookmarks. Ctrl-U did show me the actual HTML of the page it should have been rendering. A couple of restarts later and much other finageling, finally ran install program again. Could get window to render properly. Tabs open fine, but cannot get a second window to open - neither from the shortcut (or actual exectable, Ctrl-N, File - New Window, or opening a HTML document on my computer). No application features executed once in this state. i.e. OS events (maximize, minimize, close) still functioned. Menus, opening hyperlinks, and basically anything else failed to work. Even after closing the original window, Task Manager still reported a Firefox process which needed to be killed before any further use of Firefox 1.0 could take place. After several more restarts, removing all unusable extensions and some other efforts, uninstalled Firefox, restarted, and installed 1.0 again. The same new window behavior was experienced but at least it rendered content the first time it started. Finally, located 0.9.3 in my downloads folder (fortuantely I hadn't gotten around to cleaning it up lately), uninstalled 1.0 and installed 0.9.3. New window works just fine now. Fearful to install 1.0 again over my existing 0.9.3 but will next weekend if you guys want me to see if it happens again. I consider this a blocker since the normal operating state is degraded any attempt to open a second browser window requires the process to be killed manually before being able to use the program again its degraded state and using the program in its fully operational state seems impossible. It is preventing me from downgrading to 1.0 from my current 0.9.3.
Comment 2•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 3•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•