Closed
Bug 179676
Opened 23 years ago
Closed 21 years ago
Increase the Go menu history list size
Categories
(Camino Graveyard :: History, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: stf, Assigned: sfraser_bugs)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021109 Chimera/0.6+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021109 Chimera/0.6+
If you go to a lot of different pages then use the Go menu list to go back to a
previously visited page, after several go back, the Go menu list has forgot
where you have been.
I don't know if this can be increased in the current build 1109 but it would be
great to be able to specify how many pages will be stored in the Go menu history
list, even if it's by modifying a .js variable (no GUI).
Reproducible: Always
Steps to Reproduce:
| Assignee | ||
Comment 2•23 years ago
|
||
pink: what do you think?
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Updated•23 years ago
|
Component: Toolbars & Menus → History
Comment 3•23 years ago
|
||
where does the limit exist? in our shist service or in the chimera ui?
Comment 4•22 years ago
|
||
I run into this limit from time to time (which seems to be 50 entries on my
Debian 1.6). I swear that in older versions of mozilla, there was a pref in the
UI to change this limit. I also thought I could change it with
browser.sessionhistory.max_entries, but this doesn't seem to have any effect. I
can still go back only 50 pages.
Moreover, 50 is a ridiculously low limit. It would probably be sufficient to
increase the limit to 1000 or so without making it a preference.
(In reply to comment #4)
> I swear that in older versions of mozilla, there was a pref in the
> UI to change this limit. I also thought I could change it with
> browser.sessionhistory.max_entries, but this doesn't seem to have any effect. I
> can still go back only 50 pages.
See bug 197466.
Comment 6•21 years ago
|
||
Is this a history issue or just a pref that needs to be acknowledged/created?
| Assignee | ||
Comment 7•21 years ago
|
||
The Go menu has global history in it now, with as many items as you have.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Comment 8•21 years ago
|
||
in a nightly from the 15th, i get nothing in the go menu on tiger. did you
address that issue with this patch, or are you still relying on the old callback
hack?
| Assignee | ||
Comment 9•21 years ago
|
||
Hrm, the Go menu doesn't rely on any "callback hack". It just overrides [NSMenu
update]. Maybe this is no longer called on Tiger?
Comment 10•21 years ago
|
||
that's what i meant (couldn't remember the routine name). update no longer is
called on tiger.
Comment 11•21 years ago
|
||
Bahhhhh it would be nice if there was a pref to turn off/control the new
behavior, because the Go menu now takes considerably longer to open (i.e. after
you click on it); and realisticly, do we need all those days to be listed there
(especially an entry like More than a week ago)? If you're really looking for
something you might as well open up the history and search there (i.e. using cmd-Y).
Comment 12•21 years ago
|
||
Sorry for the comment spam, just realized this has been addressed in bug 291414.
just tested it now and realized that it's not only the Go menu lagging. But like
I said, a pref (even if it's just in the .js) is really needed to be able to
control this.
You need to log in
before you can comment on or make changes to this bug.
Description
•