Closed
      
        Bug 283639
      
      
        Opened 20 years ago
          Closed 20 years ago
      
        
    
  
"Sanitize Now" doesn't work if "Ask Me Before Sanitizing" is checked
Categories
(Firefox :: Settings UI, defect)
Tracking
()
        RESOLVED
        FIXED
        
    
  
People
(Reporter: dave_harper, Assigned: bugs)
Details
(Keywords: regression)
Attachments
(1 file)
| 9.63 KB,
          patch         | Details | Diff | Splinter Review | 
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050225 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050225 Firefox/1.0+
Go to Tools -> Sanitize Firefox... 
Make sure the "Ask Me Before Sanitizing Firefox" checkbox is ticked.
Try to clear History or Cache by having their tickboxes ticked, then click
"Sanitize Now"
Nothing Happens. If the "Ask me..." is unticked, then the option works as
normal. If it IS ticked then I would expect a dialogue to pop-up saying, "Are
you sure you want to clear these items? [Yes]/[No]"
Reproducible: Always
Steps to Reproduce:
1. Tools -> Sanitize Firefox
2. Tick "Warn Me" button
3. Click "Sanitise Now"
Actual Results:  
Nothing
Expected Results:  
History and Cache should be cleared, for example, after warning the user what is
about to happen
| Comment 1•20 years ago
           | ||
->New
| Updated•20 years ago
           | 
JS error after hitting "Sanitize Now" button.
Error: currentPane has no properties
Source File: chrome://global/content/bindings/preferences.xml
Line: 751
|   | Assignee | |
| Comment 3•20 years ago
           | ||
|   | Assignee | |
| Updated•20 years ago
           | 
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
| Updated•20 years ago
           | 
Flags: blocking-aviary1.1?
|   | ||
| Comment 4•19 years ago
           | ||
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs,
filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•