306005 - Server Settings pane freezes - not able to click OK or shift to another pane

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Account Configuration, defect)

Description

[Shriramana Sharma]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050824 SeaMonkey/1.0a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050824 SeaMonkey/1.0a

Not sure how old this bug is, but this seems to be related to bug #305608 which
I reported a few days ago.

When I go to Mail & Newsgroups Account Settings, and hit the Server Settings of
*any* account, I am unable to update server settings due to the OK button not
functioning. I am also unable to shift to any other pane by clicking Copies &
Folders etc. The Cancel and Help buttons do function, however. 

Hitting the OK button or trying to move to a different pane (Copies & Folderss
etc) causes the following error on my Javascript Console:
%-------------------------------------------------
Error: undefined has no properties
Source File: chrome://messenger/content/AccountManager.js
Line: 422
%-------------------------------------------------

Note that the problem exists even with a fresh test profile.

Reproducible: Always

Steps to Reproduce:
1. Goto Mail & Newsgroups Account Settings
2. Click on Server Settings of any account
3. Click on OK
4. Click on any other pane (Copies and Folders etc)
Actual Results:  
I got an error in the JSC (see details above) and the server details I changed
were not updated on hitting OK. Nor was I able to move to any other pane.

Expected Results:  
It should not have given any JSC error (right?) and should have saved my server
details and closed the window upon hitting OK. It should also have allowed me to
move to a different pane if I had so told it to.

Theme using: iCandy Junior by Aaron Spuler
Bug persists with default theme? Yes, even on fresh profile.
JSC errors: see detail

Comment 1

[Adam Guthrie]

I'm pretty sure this is a regression that is fixed in the most recent builds.
Can you test with the latest builds and confirm this is fixed?

Comment 2

[Shriramana Sharma]

(In reply to comment #1)
> I'm pretty sure this is a regression that is fixed in the most recent builds.
> Can you test with the latest builds and confirm this is fixed?

As you can see my user-agent ID, I'm using 20050824. You want me to download
20050825 and check? (Am on limited bandwidth, so asking...)

Comment 3

[Adam Guthrie]

Yes, because this regressed in the 20050824 builds.

Comment 4

[Shriramana Sharma]

In reply to comment #1
> I'm pretty sure this is a regression that is fixed in the most recent builds.
> Can you test with the latest builds and confirm this is fixed?
and to comment #3...
> Yes, because this regressed in the 20050824 builds.

Okay, this bug is fixed on 20050825 (though it did exist on 20050824). I however
found a different bug on 20050825. Local folder is not seen. Okay, this is bug
#305868 so I'm not re-reporting. 

Changing status to RESOLVED FIXED, if that's all right. Hope I'm allowed to do
this since I reported the bug...

Comment 5

[Adam Guthrie]

We usually only resolve bugs as FIXED if know what patch fixed them. WORKsFORME
is a more suitable resolution in this case.

Comment 6

[Shriramana Sharma]

Well I thought of doing that first, but I read the text at "A Bug's Life Cycle"
(https://bugzilla.mozilla.org/page.cgi?id=fields.html) and it says:

%------------------------------------------------------------------------------
WORKSFORME
    All attempts at reproducing this bug were futile, and reading the code
produces no clues as to why the described behavior would occur. If more
information appears later, the bug can be reopened.
%------------------------------------------------------------------------------

Since it's not true that "all attempts at reproducing this bug were futile", I
thought:

%------------------------------------------------------------------------------
FIXED
    A fix for this bug is checked into the tree and tested.
%------------------------------------------------------------------------------

would be better. 

I would like to know more. If possible please contact me off-bugzilla and
explain the nuances of the difference so we don't spam others with this RESOLVED
bug. Thanks.