Step to reproduce: 1) Go to the URL http://www.camtechsystems.com. 2) Let the redirect happen (you will go to the "Old Browser" page). 3) Press 'Back' 4) When the "Old Browser" page loads again, press 'Back' 5) Continue this until Mozilla enters an infinite loop of reloads (it usually only takes twice or three times). Occurs with M14 final and debug and opt builds pulled from CVS this morning at 8:30.

The JS code is executing fine each time the page is loaded. There's no script on the target page so I don't know why it's immediately going back again after the first couple of times. cc'ing radha since I don't know where this goes, sorry.

Sounds like one for Radha.

Looks conceptually similar to bug 20283, "Infinite loop when anchor has javascript:history.go(0)"

bug 20283 has a lot to it. I think maybe radha should take a look and decide whether she wants to dupe it or not.

Well, the JavaScript history does not seem to be 0 here, and it is not in an anchor. But, if it is a dup then mark it. You guys know more than me ;-)

Putting on [nsbeta2+][6/01] radar. This work must be done by 06/01 or we may pull this for PR2.

I can no longer reproduce this because the page has changed (no redirect) does anyone have (or can suggest) an independent testcase?

Move to M19.

Due to slip in schedule, moving this bug from [6/01] to [Will be minus on 6/15] for fix deadline.

Has anyone seen this recently or know of a testcase? I'd like to argue for this bug to be nsbeta2+(no date) but w/o a reproducible testcase my argument would have no merit (and rightly so).

I belive the problem is still there. However, I dunno of a test case.

Well, I tried to make a testcase, but since there are some other bugs in JS now, I cannot. Specifically, redirect pages that use document.location are not placed in the history. Oddly enough, pages that use location.replace() remain in the history.

Cleaning up status whiteboard marking beta2 minus (we're past 6/15) Note that the discussion suggests that there is no longer a test case to be had... and perhaps this should be just marked "fixed" until/unless there is a current example.

Ummm. There can't be a testcase until someone fixes the JavaScript history bugs that exist. These bugs are blocking any testing on this.

Nav triage team: [nsbeta3-]; marking dependency on 18321

*** Bug 33311 has been marked as a duplicate of this bug. ***

I don't see any redirection to teh old page in the above url. Please provide a good url

Bug 42723 is preventing me from testing this (read second comment about location = foo.bar acting like location.replace)

Adding nsbeta3 keyword to bugs which already have nsbeta3 status markings so the queries don't get all screwed up.

42723 is fixed. Most of the JS hookup with SH is done. Marking this fixed. Reopen if the problem still exists.

I need a hand here. If someone can accurately verify this fix please do. If someone can create a JS testcase that demonstrates the fix - even better.

Mass removing self from CC list.

Now I feel sumb because I have to add back. Sorry for the spam.

mass remove verifyme requests greater than 4 months old