75733 - Setting expire 0 days disables session history

Status: RESOLVED WORKSFORME

(Core :: DOM: Navigation, defect, P3)

Description

[rjh]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16 i686; en-US; 0.8.1)
BuildID:    2001041108

If history expiration is set to 0 when mozilla starts, session
history is disabled.  Back, forward are grey, go history is empty.
If changed to non-zero then session history works.

This is a change.  Recent versions, expire 0 days resulted in session
history being discarded on program quit, but did not disable history
for that particular execution.

Reproducible: Always
Steps to Reproduce:
1.Set expire 0 days
2.Quit and restart mozilla
3.

Actual Results:  No session history until expire is changed to non-zero

Expected Results:  Session history should work.  History should be discarded when
mozilla quit.

Comment 1

[Claudius Gayle]

please double-check, are you setting the 'Browsing History' to 0 days and seeing this
affect Session History, or are you setting 'Session History' to 0? Because if it's Session
history those are entries, not days and you would be seeing the correct behavior when
setting to 0 and this bug would be invalid.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Reporter, could you please respond to the questions [e-mail] asks? 
We really need more information to be able to do something useful about this bug 
(short of marking it invalid).  Please try to respond within the next two 
weeks....

Comment 3

[rjh]

The problem is more subtle than initially reported.  With 2001053108 it is very
infrequent.  When it occurs there has always been at least the following events:
 1) A page load that was interrupted by another page load from a link on that
page that is loading.
 2) A change to the preferences.

Then on some occasions, not all, the history stops working.  Multiple different
sites can be visited, with no history under the "go" and with "back"/"forward"
remaining grey.  This is not restricted to changes to the expire preferences. 
But it is not readily reproducible, so there are other factors involved.

It is now very rare.

Comment 4

[Claudius Gayle]

please answer the 4-12-01 questions...

Comment 5

[rjh]

It was browsing history.

However, the problem has now occurred for other values of browsing history.  I
now suspect some interaction between rapid page loads without waiting for the
prior to finish loading (and not using stop) together with the act of editing
preferences.  But with the more recent builds it is very rare and not at all
reproducible.

Comment 6

[Keyser Sose]

Marking NEW.

Comment 7

[Radha on family leave (not reading bugmail)]

I'm marking this WFM, as I can no longer reproduce the original problem
described here. Also, we have made the default # of entries session history will
hold as 50, so if for some reason, the prefs was corrupted, session history will
continue to work.