Closed Bug 86416 Opened 23 years ago Closed 20 years ago

Navigator->History pref dialog confusing

Categories

(Core Graveyard :: History: Global, defect)

Product:
Core Graveyard
Component:
History: Global
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED INVALID
Milestone:
Future

People

(Reporter: jmd, Assigned: bugzilla)

Details

This dialog is poorly designed. As a power user, if I'm confused, most other
users certainly will be.

We have 3 types of histories listed, browsing, location bar, session. They are
described well enough, but the actions you can take with them are nonsensical.

Two of them can be configured, and a differant two can be cleared.

Q1) Why can't I configure location bar history? Does it use the same data from
browsing history? If it does, the relationship needs to be stated.

Q2) Why can't I clear session history? This one is more minor, I suppose, since
a quit-restart will clear it, but if clearing during runtime isn't a terrible
ammount of trouble, it would make the dialog more uniform.
->alecf

what build are you using?
Assignee: asa → alecf
QA Contact: sairuh → claudius
todays linux (2001061806)
ping? 2 months, no changes to the dialog or discussion...is this waiting on the
new converged history?
reassign to default owner
Assignee: alecf → sgehani
QA Contact: claudius → sairuh
-> History: Global
Assignee: sgehani → blakeross
Component: Preferences → History: Global
QA Contact: sairuh → claudius
Target Milestone: --- → mozilla1.0
Target Milestone: mozilla1.0 → mozilla0.9.9
Target Milestone: mozilla0.9.9 → Future
When is this supposed "new history" coming? There's a lot of history bugs that
are waiting on it, apperantly. History blows right now. Almost as much as form
manager.
Status: NEW → ASSIGNED
Jeremy, is this pref pane still confusing?
Now there are only two types of history, and both can be cleared the same way.
Pretty consistent. So this is pretty much WFM, right?
If you think there still is an issue about location bar history's
configurability, please say so and either morph this bug or file a new one. But
have a look at bug 202910 and others if they don't already cover what you want.
I don't know, it's been three years, and I haven't used Seamonkey for two of
those. I'll mark the bug INVALID if you say it's changed.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Yes, it's really changed.
v
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.