Closed Bug 247447 Opened 20 years ago Closed 20 years ago

Preferences' OK button stops working when i select "Web Features"

Categories

(Firefox :: Settings UI, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 225236

People

(Reporter: luca, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040615 Firefox/0.9 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040615 Firefox/0.9 In the preferences dialog, if i select "Web Features" the "OK" button stops working (no matter what theme i am using). This is very annoying since to change anything on "Web Features" i must do it with "about:config" because the OK button to confirm any changes simply doesn't work. The Cancel button keeps working fine. The OK button doesn't work not even if later i select a different section of the preferences dialog. To make it work again i must close the preferences dialog through CANCEL or the top-right "X", reopen the preferences dialog and pay a lot of attention to not select "Web Features" for mistake. Reproducible: Always Steps to Reproduce: 1. Open the preferences dialog 2. Select "Web Preferences" 3. Click on the "OK" button Actual Results: Nothing happens, the OK button simply doesn't work anymore until the preferences dialog is closed and reopened. Expected Results: Close the preferences dialog and save the changes. Mandrake 9.2 Kernel: 2.4.22-26mdk
Do you have entries in the blocked popups list with port numbers? If so, please remove them, test again, and report the error that appears in the javascript console.
I did as you said and it works now... just... why? What has this to do with the web-features page of preferences? Thanx, Luca
in short, the definition of a valid nsIURI changed between 0.7 and 0.8, making the port no longer part of the valid value. You can't enter them like that any more, but old entries can cause problems. When you hit ok after being on that page, the function checks the sites in the list and adding the ones that don't already exist. However, when it tries to parse the invalid value, it throws an exception and the function bails. So this only affects lists from 0.7 or earlier, no new users/entries will cause the problem. *** This bug has been marked as a duplicate of 225236 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
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.