Closed Bug 182266 Opened 23 years ago Closed 23 years ago

back button not functional

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 182184

People

(Reporter: tom.kralidis, Assigned: asa)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 This problem is independent of a webpage. The back button is not clickable at any point in the app. This may or may not apply to the forward button as well. The functionality to navigate back also applies to a 'right-click' action in attempting to navigate back. The option is greyed out. Reproducible: Always Steps to Reproduce: 1. Run Mozilla 2. navigate to any URL 3. click any link on link on that page for a new URL 4. see back button not working Actual Results: I was unable to navigate backwards in Mozilla Expected Results: Mozilla was expected to navigate to the previous viewed webpage
Check bug 126826 and bug 164407. I haven't read through all of those bugs but this seems like the sort of problem that might be solved by either: a) Creating a new profile (or possibly deleting compeg.dat per bug 164407, although that should be fixed now). b)Increasing the value of Session history per bug 126826 <--this sounds like the most likely problem c)Reinstalling Mozilla (particually if you installed over a previous build) I suggest you check the other bugs and mark this as a duplicate of one of those if appropriate.
Please close Mozilla and delete your history file and try it again.
bug 182970 was resolved as dupe of bug 126826, but I think this is actually a new regression (happens in recent builds around mid or late November). Should we keep one of these new bugs open and identify what the problem is?
*** This bug has been marked as a duplicate of 182184 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.