Closed
Bug 432724
Opened 16 years ago
Closed 1 year ago
In Privacy tab of Preferences, "Download History" should be dependent on its "Browsing History" parent
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: stephend, Unassigned)
References
Details
(Keywords: dataloss)
Attachments
(1 file)
2.95 KB,
patch
|
Gavin
:
review-
faaborg
:
ui-review+
|
Details | Diff | Splinter Review |
See https://bugzilla.mozilla.org/show_bug.cgi?id=432427#c1 Build ID: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9pre) Gecko/2008050704 Minefield/3.0pre Summary: In Privacy tab of Preferences, "Download History" should be dependent on its "Browsing History" parent Steps to Reproduce: 1. Go to "Preferences"/"Options", "Privacy" tab, and click on the "Settings..." button under "Private Data" 2. Examine the preferences for "Browsing History" and "Download History" Expected Results: As in the "Tools", "Clear Private Data" dialog, "Download History" should be dependent on "Browsing History"--it should be inset, and, if you select "Browsing History", it should be checked. Actual Results: "Download History" and "Browsing History" are on separate lines and there's no dependency.
What, at first, seems to be a minor bug, may in fact have huge consequences: Suppose you wanted to clear your browsing history, but actually KEEP your download history, this is no longer possible: FF3 will always clear both. The way I see it, the real bug is not the checkbock which is not inset and greyed out (although this is confusing). The real bug is that there is no way to maintain your list of downloaded files and still clear your browsing history. This was possible ion FF2. (I think, therefore, that Bug 45398 is only in parts a duplicate; it also mentions the dependency of the "download history" on the "browsing history" as malfunction.)
Comment 4•16 years ago
|
||
(In reply to comment #3) > The real bug is that there is no way to maintain your list of downloaded files > and still clear your browsing history. FTR: That's bug 456395.
Comment 5•16 years ago
|
||
the "Remember What I've downloaded" option on the Privacy tab should probably also be dependent on the history option above it, should i file a separate bug?
Comment 7•15 years ago
|
||
(In reply to comment #3) > What, at first, seems to be a minor bug, may in fact have huge consequences: > Suppose you wanted to clear your browsing history, but actually KEEP your > download history, this is no longer possible: FF3 will always clear both. > > The way I see it, the real bug is not the checkbock which is not inset and > greyed out (although this is confusing). The real bug is that there is no way > to maintain your list of downloaded files and still clear your browsing > history. This was possible ion FF2. (I think, therefore, that Bug 45398 is only > in parts a duplicate; it also mentions the dependency of the "download history" > on the "browsing history" as malfunction.) That is the intended behavior from bug 251337
Comment 8•15 years ago
|
||
...but see also bug 465995.
Updated•15 years ago
|
Comment 9•15 years ago
|
||
Make the Downloads checkbox dependent on the History checkbox.
Attachment #422874 -
Flags: review?(gavin.sharp)
Updated•15 years ago
|
Attachment #422874 -
Flags: ui-review?(faaborg)
Comment 10•15 years ago
|
||
This shouldn't need UI review. It's clearly a bug in our code.
Comment 11•15 years ago
|
||
The dependency needs to be visually apparent by indenting the download history option, similar to how third party cookies is indented under accepting cookies.
Comment 12•15 years ago
|
||
(In reply to comment #11) > The dependency needs to be visually apparent by indenting the download history > option, similar to how third party cookies is indented under accepting cookies. I thought that at first, but wouldn't it be odd given the current grid layout? Indenting that control would make the entire checkbox set to appear as randomly positioned, IMHO.
Comment 13•15 years ago
|
||
Yeah visually it really isn't great, but it does make the dependency more expected. I don't have a strong opinion, especially if we are able to eventually decouple these so that there isn't a dependency in the future.
Comment 14•15 years ago
|
||
Comment on attachment 422874 [details] [diff] [review] Patch (v1) ui is fine to prevent dataloss, but ultimately we should get these to no longer have a dependency.
Attachment #422874 -
Flags: ui-review?(faaborg) → ui-review+
Comment 15•15 years ago
|
||
(In reply to comment #14) > (From update of attachment 422874 [details] [diff] [review]) > ui is fine to prevent dataloss, but ultimately we should get these to no longer > have a dependency. Of course, doing this would regress bug 251337
Comment 16•15 years ago
|
||
(In reply to comment #15) > (In reply to comment #14) > > ultimately we should get these to no longer have a dependency. > Of course, doing this would regress bug 251337 I don't think that's necessarily true. Either way, that's what bug 465995 is about.
Comment 17•14 years ago
|
||
Fixing this bug will caused unintended and (to the user) unexpected data lost.
Updated•14 years ago
|
Whiteboard: [has patch][needs review gavin]
Comment 18•13 years ago
|
||
Gavin: ping?
Comment 19•13 years ago
|
||
Comment on attachment 422874 [details] [diff] [review] Patch (v1) Seems like we should combined these into a single pref using the same approach as bug 490030 comment 8: turn the history checkbox into "Browsing and Download History", and then just hide/remove the download checkbox.
Attachment #422874 -
Flags: review?(gavin.sharp) → review-
Comment 20•13 years ago
|
||
There's a little chance that I can work on this in any reasonable amount of time. Throwing it back into the pool.
Assignee: ehsan → nobody
Status: ASSIGNED → NEW
Whiteboard: [has patch][needs review gavin]
Comment 21•1 year ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: major → --
Updated•1 year ago
|
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•