User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b4) Gecko/20090423 Firefox/3.5b4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b4) Gecko/20090423 Firefox/3.5b4 When I loaded the new version my all history, and bookmarks disappeared. The history did not begin to fill in even after going to several pages. The history did not fill as I went from location to location. After several attempts to locate a possible fix for the I also noticed that the back a page button on will not allow you to back up a screen from the tab that you are working in. The only way to go backwards was to close the tab and reload where I was going. Reproducible: Always Expected Results: (1) I expected like in the last loads that the bookmarks would sync. (2) I would expect to see a history for the day to show with the ability to load a history from another day if needed. the history should fill in like the bookmarks upon upgrade of the version like the last version did. (3) I would expect that if you go from one page to the next that you should be able to use the back screen button after the first page. (1) I would like to have a button in the bookmarks tab that if the bookmarks did not load for some reason that there was a manual sync button.
Please read: http://support.mozilla.com/en-US/kb/Bookmarks+and+toolbar+buttons+not+working+after+upgrading
Version: unspecified → 3.5 Branch
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.