Closed
Bug 17049
Opened 25 years ago
Closed 25 years ago
[Dogfood] Composer files not included in install
Categories
(Core :: DOM: Editor, defect, P3)
Tracking
()
VERIFIED
FIXED
M11
People
(Reporter: michaell, Assigned: rubydoo123)
References
Details
(Whiteboard: [PDT+])
Steps: 1) Click on message header to display message. 2) Click the "reply" button -- nothing happens. 3) Click the "reply all" button -- nothing happens. 4) Select "reply" from the "message" menu -- nothing happens. Using build #1999102110
Updated•25 years ago
|
Assignee: phil → ducarroz
Comment 1•25 years ago
|
||
Reassign to ducarroz, cc alecf
Comment 2•25 years ago
|
||
It also happened on the Linux platform for today's commercial build (10-22-08-M11)
Linux(1999-10-21-08-M11)and (10-22-08-M11) win_nt (1999-10-21-11-M11)and (10-22-09 M11) Mac (1999-10-21-09-M11) I have seen this on yesterday and today's build. I can click on Reply or Reply-All to open the compose window. But the To field is empty (see bug 17025) and I cannot type in Body (see bug 16931) This only happens on using the HTML compose editor though.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Comment 4•25 years ago
|
||
I have just installed the official build from today on Windows and button Reply or Reply All bring a message compose window. Of course, we cannot edit the reply (bug 16931) and the to field is empty (bug 17025). Despite those bugs, everything is "fine" for me! michaell, could you explain me why to you mean by "nothing appends"? What does you output window (the black dos window) say?
Reporter | ||
Comment 5•25 years ago
|
||
This was using yesterday's build. I'll try it using todays soon. I actually see no mail compose window come up at all. I click the buttons or select the menu items and there is no activity on the screen whatsoever.
Reporter | ||
Comment 6•25 years ago
|
||
Still happening with build # 1999102208
Comment 7•25 years ago
|
||
That's exactly the build I am using, with a brand new profile. michaell, it's very important that you give me the content of your output window once (wait 10-20 secs) you have pressed the reply button. Thanks
Updated•25 years ago
|
Target Milestone: M11
Reporter | ||
Comment 8•25 years ago
|
||
It says: "MsgReplyMessage from XUL ComposeMessage from XUL i = 0"
Reporter | ||
Comment 9•25 years ago
|
||
Actually, I can't bring up a plain message compose window, either.
Reporter | ||
Comment 10•25 years ago
|
||
...using the "new message" button.
Comment 11•25 years ago
|
||
Very strange, messenger compose is never started! But the reply button action is fired. Something looks like very brocken in your install. Try this: 1) delete the file component.reg, it's a the same level that mozilla.exe 2) start mozilla again and do a new message if it still not working, I will come to see you Monday.
Comment 12•25 years ago
|
||
QA, are you able to reproduce this problem?
Comment 13•25 years ago
|
||
No, we don't have a problem with the compose window not appearing in today's build. michael - can you start apprunner with the -compose flag?
Comment 14•25 years ago
|
||
michael - are there other areas of the product where there are buttons that you can click to invoke another window? If so, does that work for you?
Comment 15•25 years ago
|
||
The button woks because we get the following output wich is executed when messager receive the reply command: MsgReplyMessage from XUL But for some reason, the script never reach the line where we open the compose window (or this call failed). What strange here is that we don't get any error message in the output window!
Reporter | ||
Comment 16•25 years ago
|
||
Hmmm. I'm not able to open a compose window, but I am able to open a new Nav window and I'm able to open Messenger from Navigator. I'll try deleting my component.reg file.
Comment 17•25 years ago
|
||
Must be reproducible for dogfood. PDT-
Reporter | ||
Updated•25 years ago
|
Whiteboard: [PDT-]
Reporter | ||
Comment 18•25 years ago
|
||
Sorry I've been quiet on this. I just deleted everything - all of seamonkey, all of my user profiles, and the mozregistry.dat file - and reinstalled. I still cannot access any kind of composition. I also tried to launch mozilla with the -compose flag, to no avail. I think this means that I have a reproducable case of the bug, at least on my machine. Therefore, I'm removing the [PDT-] designation from the status bar
Updated•25 years ago
|
Whiteboard: [PDT-]
Comment 19•25 years ago
|
||
[PDT-] means that was an approuved second category dogfood bug. I am putting it back.
Reporter | ||
Updated•25 years ago
|
Assignee: ducarroz → beppe
Status: ASSIGNED → NEW
Component: Front End → Editor
Product: MailNews → Browser
QA Contact: lchiang → gerardok
Summary: [Dogfood] Can't reply to a message → [Dogfood] Composer files not included in install
Whiteboard: [PDT-]
Reporter | ||
Comment 20•25 years ago
|
||
OK. I've figured out what's going on. The Ender team has not synched up with the install team to ensure that all of their files are being included in the isntall. I am reassigning the bug to Beppe and changing the QA contact to Gerardo. I'm also changing the summary to reflect the accurate status. Cc'ing Cathleen. Removing PDT- designation. All this does is makes sure that the PDT team reexamines the bug with the new information for inclusion in "dogfood" status.
Comment 21•25 years ago
|
||
Approved for PDT+ :-)
Assignee | ||
Comment 22•25 years ago
|
||
getting the data together with a list of any new files that may be introduced in the near future. I'll pass the data on to Cathleen as soon as I get it compiled.
Assignee | ||
Comment 23•25 years ago
|
||
*** Bug 17383 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 24•25 years ago
|
||
sent the list of Composer files to Cathleen. Once they get incorporated into the installer, the install will need to be tested to ensure composer launches correctly.
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 25•25 years ago
|
||
Build 1999102808M11: Win32/NT4 Overview: I am unable to open the Compose window by selecting the "New Msg" button or File/New Message. I can select Tasks/Composer and the Editor window appears. The Compose window launches for me if I extract the files using mail.xpi but not with a seamonkey32e.exe installation. Steps to Reproduce: 1. Download the seamonkey32e.exe file to a temp directory 2. Run the "seamonkey32e.exe" file so the installation begins. 3. When the installation prompts for a directory path change it from the default. I used c:\32nt4\seamonk. 4. The end of the installation automatically launches the Profile Manager so select a profile that has already been migrated. 5. Start Mail 6. Select the "New Msg" button 7. From the menu select File/New Message Actual Results: Nothing happens. The Compose window does not launch. The console states "ComposeMessage from XUL". Expected Results: I would have expected a Compose window to appear. Additional Information: - The Compose window launches for Esther running Win95 and Fenella running NT4 after running the seamonkey32e.exe installation. - The placement of the Taskbar buttons are slightly different on systems where the Compose window launches and where it doesn't launch. On systems that work (i.e. Esther and Fenella's) there is more space between the "New Msg" and "Reply" button. There is also more space between the "Forward" and "Next" button. On my system, where it does not work, all the taskbar buttons are evenly spaced. - I tried a basic install - I tried a complete install - I tried an existing profile (pop and imap) - I tried a migrated profile - I tried deleting the registry file and the user profiles and migrating again - I tried launching with "mozilla.exe -installer" and creating a new profile.
Comment 26•25 years ago
|
||
If I can get someone from Mail QA or even michaell to verify this bug, that would be great...
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 27•25 years ago
|
||
It now works for me. Marking verified.
Assignee | ||
Comment 28•25 years ago
|
||
linking to PDT+ tracking bug 12658
You need to log in
before you can comment on or make changes to this bug.
Description
•