Closed Bug 323966 Opened 19 years ago Closed 18 years ago

Users expect clearing history to clear searchbar also

Categories

(Firefox :: Search, defect, P3)

2.0 Branch
defect

Tracking

()

RESOLVED FIXED
Firefox 2 beta1

People

(Reporter: celticone, Assigned: Waldo)

Details

(Keywords: fixed1.8.1, privacy, Whiteboard: [swag: 0d])

Attachments

(1 file, 1 obsolete file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

The google search bar dropdown box shows searches for weeks and will not clear
even though the option is to clear all data on exit. 

Also, option in Advanced Privacy to clear history is not functional

Reproducible: Always

Steps to Reproduce:
1.Open Firefox
2.Check google search bar dropdown history
3.

Actual Results:  
I simply reopen Firefox and check the google search bar drop down, *all* searches
remain, they *never* clear

Expected Results:  
The same searches are *always there, they *never* clear

How about *clear* the history as it's set to do
The google searchbar is saved form data. "Browsing history" refers to the list of sites you've visited--the data that appears if you view the History sidebar.

If I check the "saved form information" box on the "Clear private data" screens my search box history is cleared, just as it is in the drop-down on the Google page itself. Are you using the right option?
Keywords: privacy
Whiteboard: [sg:needinfo]
As originally written the bug is "worksforme" -if- you know the search field is form data. But it's not at all obvious and we've gotten several complaints along this line. Users think of that box as browsing history -- they enter things and pages open just like the URL bar it sits next to. It certainly isn't part of a web page (form).

There may be a dupe although I couldn't find it (bug 318058 is along similar lines, but describes problems even if you know it's form data you need to clear).

I'm morphing this into a UI design bug to reconsider how this works. UI that surprises people is UI that needs help.
Group: security
Severity: major → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking-firefox2?
Keywords: uiwanted
Summary: Google searchbar history will not clear → Users expect clearing history to clear searchbar also
Whiteboard: [sg:needinfo]
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → 2.0 Branch
Dan is right. Anything in chrome is not "form data" to the user, it's something else. Of the current options, "Browsing History" seems like the right one to put it under.

Gerv
Not a lot to add here. The right way to do this is to consider the search history to be the same thing as the browsing history (which is more or less correct even technically, since search results are part of the browsing history), or to add a separate field for Search History, although my personal feeling is that this latter solution is overkill.
Keywords: uiwanted
Severity: enhancement → minor
Flags: blocking-firefox2? → blocking-firefox2+
Keywords: helpwanted
Target Milestone: --- → Firefox 2 beta1
It's easy to make "Clear History" also clear only the search bar form history, but not so easy to prevent "Clear Form Data" from clearing the search bar history, since it calls "removeAllEntries" on nsIFormHistory.
Seems to me that it's sufficiently ambiguous that clearing it in both cases (when clearing form data and when clearing history) is reasonable, as well as being easy.
Ok, here's a patch that does that. Any other opinions on this proposed behavior (comment 6)?
(In reply to comment #7)
> Created an attachment (id=223871) [edit]
> clear search bar history and undo stack for both "clear history" and "clear
> form data"
> 
> Ok, here's a patch that does that. Any other opinions on this proposed behavior
> (comment 6)?

I'd rather not have two options delete the same history, as it makes it twice as hard for the user to figure out what deletes what.

If it's seriously hard to do this due to the way we store search data, I'd recommend relabeling the option to "Saved Form and Search History", instead.
So, I think we might need to accomodate room for a separate pref for searchbar autocomplete as part of the pref redesign discussions, since there's a desire to have searchbar autocomplete on without in-page formfill.
Assignee: nobody → jwalden+bmo
Priority: -- → P3
This looks like it would have been (slightly hackishly) possible using the nsIFormHistory interface as documented on XULPlanet; unfortunately, that interface hasn't existed since January 26, and the replacement provides no support for accessing values in form history.  I think support could be readded without too much effort by partially reverting the removal of that functionality, but this solution would be a hack, and I personally don't think it's worth the effort.

Long-term, I think the solution here is to make search history use its own table in storage somewhere, separating search results from other form history.  For now, tho, I think the most expedient solution is simply to change the wording in the dialog to actually reflect what happens.
Status: NEW → ASSIGNED
Attachment #223871 - Attachment is obsolete: true
As recommended in comment 8...
Attachment #224269 - Flags: ui-review?(beltzner)
Attachment #224269 - Flags: review?(mconnor)
Keywords: helpwanted
Whiteboard: [swag: 0d]
Comment on attachment 224269 [details] [diff] [review]
Change the label to "Saved Form and Search History"

Jeff, can you open a followup to track your long-term suggestion? I agree that we'd like to offer more granularity here if possible in the future.

Also, note that bug 340677 now asks users if they want to "Remember what I enter in forms and the search bar", which balances this sanitize option.
Attachment #224269 - Flags: ui-review?(beltzner) → ui-review+
Attachment #224269 - Flags: review?(mconnor) → review+
Comment on attachment 224269 [details] [diff] [review]
Change the label to "Saved Form and Search History"

(In reply to comment #12)
> Jeff, can you open a followup to track your long-term suggestion?

See bug 341268.
Attachment #224269 - Flags: approval-branch-1.8.1?(mconnor)
Attachment #224269 - Flags: approval-branch-1.8.1?(mconnor) → approval-branch-1.8.1-
Attachment #224269 - Flags: approval-branch-1.8.1- → approval-branch-1.8.1+
Fixed on trunk and branch.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Keywords: fixed1.8.1
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: