Search and form history should be separate preferences
Categories
(Toolkit :: Data Sanitization, enhancement)
Tracking
()
People
(Reporter: 52qtuqm9, Unassigned)
References
()
Details
Right now I can tell Firefox to remember search and form history or neither search nor form history.
I want to be able to tell it to remember search history but not form history.
By search history in this context I mean things I search for in the URL bar.
Mark, since OP picked the incorrect component and nobody ever triaged this bug, maybe you can mark it as a duplicate of Bug 1962888? I've given an example of why this separation is necessary, especially in light of Bug 1650874.
Comment 2•1 year ago
|
||
Generally we prefer to mark as duplicate of an older bug, because that will have been tracked more. However as a one-off I think this is reasonable to dupe forward.
| Reporter | ||
Comment 3•1 year ago
|
||
I don't understand why this was marked as a duplicate. This bug is about separating search history from form history, which as far as I can tell is orthogonal to and not mentioned in bug 1962888. Can someone please clarify?
| Reporter | ||
Updated•1 year ago
|
I suggested marking it as a duplicate because:
- OP picked the wrong component and nobody has moved it to a more appropriate one yet
- The GUI for selecting what to remember or clear has just recently been rewritten, and the dev team actually wanted to make it less granular at first (Bug 1888466), so I didn't think you'd be interested in making it more granular now. If you are, that's great
Until this option is added, users can actually disable the display of search history suggestions by setting browser.urlbar.maxHistoricalSearchSuggestions to 0. Again, if you are interested in offering an option to disable the recording of these entries without also affecting webpage forms, that's great.
Please move this bug to the Toolkit :: Data Sanitization component.
Updated•1 year ago
|
Comment 5•11 months ago
•
|
||
This has been fixed in Bug 1888466. Feel free to reopen this if this does not cover this bug!
Description
•