Closed Bug 288196 Opened 20 years ago Closed 15 years ago

Back Button stops working sometimes

Categories

(SeaMonkey :: General, defect)

SeaMonkey 1.1 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: gstoett, Unassigned)

Details

(Whiteboard: bugday0420)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.6) Gecko/20050319 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.6) Gecko/20050319 i have no further details for this bug, because i have no clue what exactly causes this problem. only thing that i have noticed as sidekick of this bug is that at the same time when the back button stops working sometimes the text in the adress bar is disappearing also (not always though). only extra thing to mention is probably that this only happened to me when i had more then one tab open (but cant say if it would happen also with only one tab). sorry for the lack of more useful information Reproducible: Sometimes
Perhaps side effects of this bug, look at the dependency list: Bug 203960 Make bookmark groups conditionally replace existing tabs instead of appending This shouldn´t happen with the non-default setting of Edit->Preferences->Navigator->TabbedBrowsing When opening a Bookmark Group: [x] add tabs [ ] replace existing tabs With the default setting of 'Replace' going Back can´t work in all cases, it can´t go back to a dynamically generated page, the page will be newly generated, and sometimes that is impossible. The previous default of adding tabgroups didn´t need going back, as there was nothing replaced, and another advantage was that you could load multiple short grouips. Can you try the setting above and report, if that solves your problem?
i never used the default("replace") setting, always use/used the "add" setting.
can you try a trunk build (1.8b, or suite 1.0a should be available soon)? are there any errors in the JS Console when this happens?
(In reply to comment #3) > can you try a trunk build (1.8b, or suite 1.0a should be available soon)? > are there any errors in the JS Console when this happens? where is the js(javascript?) console in mozilla 1.7.6? i am using suns java 1.5.0.2 is it possible that any of the extensions i use (adblock, googlebar, chromedit) causes the problem? or the orbit 3+1 theme?
> is it possible that any of the extensions i use (adblock, googlebar, chromedit) > causes the problem? or the orbit 3+1 theme? it's very possible. Please try without them (theme would be my first guess). js console is in tools->web development->js console
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
this bug is still there, even in Mozilla 1.7.12. only happens with tabbed browsing and more than one tab open. not only back button stops working, the adress bar also doesnt show the correct adress when switching tabs (it always shows the same adress or blank).
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
This sounds a lot like bug 157145.
Is this still an issue in recent versions of SeaMonkey (http://www.seamonkey-project.org/releases/)?
It is still there, even in Seamonkey 1.1.9 Happens rarely anyways, i just close Seamonkey and restart it when it happens, i got used to this issue over the years :)
Version: unspecified → SeaMonkey 1.1 Branch
SeaMonkey 1.1 is at end-of-life since March 1. Unless this bug can be reproduced on Sm 2.0.4 or later, it should be closed WONTFIX or WORKSFORME.
Whiteboard: bugday0420
Marking WFM. Please only reopen if you can reproduce the problem with SeaMonkey 2.0 or later, SeaMonkey 1.1 is no longer supported.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.