Closed Bug 273088 Opened 21 years ago Closed 20 years ago

If bookmark file not available when Firefox starts, Firefox window bounces up and down slightly

Categories

(Firefox :: Bookmarks & History, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: tmorehen, Assigned: vladimir+bm)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 If the bookmark file is not available when Firefox starts (ie is deleted or if on a disconnected network drive), the Firefox window bounces up or down, or shimmies up and down. This occurs whether the bookmarks sidebar is displayed or not. I can also confirm bug 251692. My bookmarks are on a network drive. One of my PCs had trouble connecting to that drive. I'd opened Firefox (it started to shimmy), followed by Windows explorer. I then clicked on the missing drive, which restored the connection. I then exited Firefox, which wrote a blank bookmark file over top of my shared bookmarks. Reproducible: Always Steps to Reproduce: 1.Delete bookmarks.html and bookmarks.bak 2.Start Firefox 3. Actual Results: Firefox showed a blank bookmarks sidebar. The firefox window shimmied, ie everything below the title bar bounced up and down slightly. It was like the menu bar height increased and decreased at half second intervals. Expected Results: Firefox should show a blank bookmarks sidebar. The window should have been steady. Firefox should not overwrite a bookmark file with a blank file if the blank file was created because a drive mapping did not exist when firefox started but was restored before Firefox exited. My drive mapping problem was due to an improper entry in my Hosts file. That's fixed now so drives map properly on login. I restored my bookmarks file from a backup so nothing was lost.
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/
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: 20 years ago
Resolution: --- → EXPIRED
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → bookmarks
You need to log in before you can comment on or make changes to this bug.