Tracking bug for all the cases and scenarios in which the "OK" button ceases to function in Preferences

Under Edit/Preferences, once you have viewed "Composing Messages", not only will the OK button cease to work, but you are unable to view any other topic in the dialog.

Hi Katherine: this is a meta (aka tracker) bug used to track all of the times in which the OK button in preferences doesn't work. Bugs for individual issues should be reported separately and marked as blocking this bug, not reported in comments to this bug. So, please file that issue as a new bug and mark it as blocking this one (40891). Thanks.

i know this is a meta bug, but rather than listing every single instance/bug in the relnotes for beta2, i'd rather the user refer to this one for the list. pls remove relnote2 kw after we ship beta2.

Well actually, I think every bug is fixed in the branch bits except bug 40884. So we should probably just relnote2 that one (correct me if wrong)...

Looks like 40884 is resolved, so I'm omitting this one from the PR2 release notes.

Well, I'm not sure if that helps but...anyway: When changing only an option at a time, without browsing in more than one categories, and then clicking OK, it usually (always?) works. If one browses into many Prefs categories or changes more than one options and then clicks OK, most chances are this button won't work.

->mcafee taking qa contact. file protests if needed. ;)

nav triage: nsbeta1-

Over to vishy to find an owner.

nav triage team: most of the issues are done, marking p5 and nsbeta1+ already at mozilla1.0

taking

Build 2001111706 for Linux, triggered by changing the monospace font from "12" to "14". Fails every time.

Build ID: 2001112009 Win2000 Select Preferences In the left pane select: Appearance Fonts Colors Themes Contacts Now click OK... Nothing happens - must cancel

Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)

This is just a meta bug. back to 1.0, adding magic keyword

Note: bug 89576 would reduce the chances of future errors.

->1.0.1

*** Bug 134132 has been marked as a duplicate of this bug. ***

I can't quite figure out what is going on with this bug, but I am not having the issue mentioned. I am currently running daily build 2002080807. Although I have been upgrading to a new daily build every day for the last several months, but only on today's build did I start having a problem with the preference dialog. What happens is this: I can open the preference dialog and edit the first page on it (Navigator), but the ok button does not work if I switch to any other page. This problem may have been present in the last few builds but I would not have noticed because I don't frequently modify my preferences. The only reason I was changing preferences this time was because I have just re-formatted my machine and installed a fresh copy of Win XP and went directly to todays build instead of upgrading from day to day. This is the error which appears in the JavaScript Debug Console: Error: document.getElementById("startupPage") has no properties Source File: chrome://communicator/content/pref/pref-navigator.js Line: 141 I hope this is the correct place to post this problem. This bug seems to be the center point of several related bugs with the preference dialog, but none of the others seems recent (at lease not that I found from the ones I went through).

Post a new bug, and make it block this one (I have the same problem)

This bug still exists as of the "stable" release of Mozilla 1.1. I've found that if you change the SMTP servers and press OK on the SMTP server "Advanced" dialog, the OK button on the Preferences page will not work, but if you press Cancel on the "Advanced" dialog, the OK button will work on the Preferences page.

This is a metabug, please file a dependant bug for any new occurrences.

This didn't occur for me in Phoenix (0.4, 0.5) until I installed a bunch of Extensions. Disabling them doesn't seem to help. I have the following extensions installed: Alternate Stylesheets, autohide toolbox, digger v0.3.0, Linky, Nuke Image, Preferences Toolbar, QuickPrefs v1.0, cssmenu v0.1.0, Tabbrowser Extensions, Text Links, UA String Widget.

I believe this will reproduce the problem. Running Fb 0.7 (I know, Fb, but I've had this problem since almost the first time I tried Mozilla Browser) on Win XP Pro. Do the following in Preferences. 1. Change cache size. 2. Add site to allow popups, starting blank. 3. Change an option in Browsing under Advanced.

All tracked bugs in this tracking bug are closed, marking fixed