175624 - Mail-composer fails to work

Status: VERIFIED FIXED

(MailNews Core :: Composition, defect)

Description

[Patrick Smits]

Every time starting a new message (or replying to a message) the mail-compose
window opens, however composing/editing is not possible. In detail:

- the 'From' field displays '...', no alternative is presented when clicking the
drop-down button

- none of the buttons (Send, Adress, Attach, Security, Save) are functioning,
although they are displayed in black (as being selectable)

- none of the menu-functions in the Edit/View/Insert/Format/Options-menu are
functioning, although they are displayed

- only the 'New'-option in the 'File'-menu is functioning

- choosing an adres in the 'To'-field is not possible, however it is possible to
edit this field (i.e. typing the email-adress manually)

- editing the 'Subject'-field works fine

- editing the message-body is not possible, no cursor appears, there's no
response to the keyboard 


Additional information:
This build: 2002101612 on Windows 98
Reported error occured after installing the 1.2 Beta release. The 1.1 release
doesn't seem to have this problem.

Comment 1

[Jean-Francois Ducarroz]

the build form October 16 is bogus. Try a new build and your problem will go away.

Comment 2

[Patrick Smits]

Attachment: Mailcomposer failure screenshot

Comment 3

[Patrick Smits]

Tried build 2002110808 but the problem appears to be unsolved in this build.
Take a look at the screenshot, something strange also happens in the format-menu
(ctrl+shift+y, ctrl+shift+k menu-items are missing).

Comment 4

[Jean-Francois Ducarroz]

-->over to varada

Reporter, have you tried to create a new profile? something looks wrong with the
profile?

Comment 5

[Patrick Smits]

Tried to create a new profile, but the profile manager failed to do so. Then I
uninstalled Mozilla and renamed the Mozilla-directory under Windows\Application
data into something different. I reinstalled Mozilla 1.2 and this time I was
able to create a new profile. I copied the files in the old profile-directory
(except the 2 .dat files, registry.dat and pluginreg.dat) to the new one and
changed the directory-references in the prefs.js file into the new ones. And now
it seems to work just fine! 

Comment 6

[esther]

I did not see the probem the reporter did, however it now works for him and he
has resolved it fixed.  I will verify it based on that.  If this problem should
show up again, please reopen with new info.