217970 - OK button in prefs dialog doesn't always work

Status: RESOLVED WORKSFORME

(Firefox :: Settings UI, defect)

Description

[Dan Soper]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5b) Gecko/20030827
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5b) Gecko/20030826 Mozilla Firebird/0.6.1+

This is similar to Bug 143359, but not, IMHO, a duplicate.

Sometimes, particularly when I've made several changes in more than one pane,
the rpefs dialogue's "ok" button does nothing. "Cancel" still works to dismiss
the dialogue, but of course all the changes are lost.

(Workaround: implement the changes one by one, ok-ing each in turn.)

Reproducible: Sometimes

Steps to Reproduce:
1. Open prefs window
2. make a few changes to various things
3. click OK

Actual Results:  
nothing. Nada. Zilch.

Expected Results:  
close dialogue and implement changes.

This problem has occured with a number of older Mozilla builds. Most recently
seen by me in the Firebird nightly 20030826.

Filing as "normal" not "minor" 'cos although the workaround is easy, it's
tedious, and since any new user's first action is likely to be to open the prefs
dialogue to set up proxies etc., this is a bug they'll see straight away, and,
umm, first impressions count, as they say. :-)

Comment 1

[Bruce Davidson]

Reporter, are you reporting this problem on Mozilla Application Suite or Mozilla
Firebird? The build ID in your bug report indicates probably firebird, in which
case the "Product" field should be set to "Firebird" so that the correct people
see the bug!

Also note the tracking bug 40891 for this sort of problem.

Comment 2

[Dan Soper]

Thanks Bruce....

Adding "blocking 40891" and setting Product to "Firebird". But I have seen this
problem with Mozilla in the past.... :-)

Comment 3

[Simon Paquet [:sipaq]]

*** This bug has been marked as a duplicate of 217300 ***

Comment 4

[Dan Soper]

Umm. I'm not sure why this was marked as a duplicate of 217300.... That appears
to be about Themes and Extensions. This bug has nothing to do with either, as
far as I can see: I use default themes, and have installed no others; and I
haven't installed any extensions. 

I also do not think, incidentally, that this bug is a dupe of Bug 215707.

Comment 5

[Mike Connor [:mconnor]]

Its not a dupe of 217300, but it is either a dupe of bug 215707 or a result of
the bustage with that specific build due to blake doing some prefs-wide changes.
 Breakage was expected and is now resolved.

Doesn't block 40891, that's a tracker for Seamonkey Prefs UI.

Please try again with a current nightly and reopen only if you can replicate
this without touching the themes panels.

Comment 6

[Mike Connor [:mconnor]]

sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs,
filter on "beltznerLovesGoats" to get rid of this mass change