Closed
Bug 320650
Opened 19 years ago
Closed 19 years ago
'Send' does not work after Ctrl+E
Categories
(SeaMonkey :: MailNews: Message Display, defect)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: toscha, Assigned: mcsmurf)
Details
(4 keywords)
Attachments
(1 file)
1010 bytes,
patch
|
iannbugzilla
:
review+
Bienvenu
:
superreview+
neil
:
approval-seamonkey1.0+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051217 Firefox/1.6a1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051217(04) SeaMonkey/1.5a Re-open a newsgroup posting via Ctrl+E from the send folder. Try to re-send. Send does not work via Send-button or via menu 'Send now'. However, it does work for mails. Reproducible: Always Steps to Reproduce: 1. Create a newsgroup posting and send, e.g. to de.test 2. Go to send folder and open same posting via Ctrl+E 3. Klick Send-button Actual Results: Nothing. Expected Results: Posting should be send again. Seamonkey 1.5a with Classic theme. Btw, it would be easier to file a bug like this if there would be an entry for 'Editor' in the component area...
Comment 1•19 years ago
|
||
(In reply to comment #0) > Re-open a newsgroup posting via Ctrl+E from the send folder. Try to re-send. > Send does not work via Send-button or via menu 'Send now'. I can confirm that. > Btw, it would be easier to file a bug like this if there would be an entry for > 'Editor' in the component area... 'MailNews: Main Mail Window' fits a little bit more than 'General' (IMHO)
Comment 2•19 years ago
|
||
I get this when I hit "Send" SendMessage from XUL GenericSendMessage from XUL Identity = [nsIMsgIdentity: id9] *** Failed to get string subjectDlogTitle in bundle: chrome://messenger/locale/messengercompose/composeMsgs.properties An error occurred executing the cmd_sendButton command [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIStringBundle.GetStringFromName]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: XStringBundle :: getString :: line 17" data: no] With Mozilla 1.8b1, I get a dialog that says "Sending of message failed. No recipients were specified. Please enter a recipient or newgroup in the addressing area." ==> composition
Assignee: general → nobody
Status: UNCONFIRMED → NEW
Component: General → MailNews: Composition
Ever confirmed: true
OS: Windows XP → All
Product: Mozilla Application Suite → Core
QA Contact: general
Hardware: PC → All
Version: unspecified → Trunk
Assignee | ||
Comment 3•19 years ago
|
||
This at least fixes the issue mentioned in Comment 2, easy review i guess. That is a regression from Bug 294140.
Assignee | ||
Updated•19 years ago
|
Attachment #206206 -
Flags: review? → review?(iann_bugzilla)
Component: MailNews: Composition → MailNews: Main Mail Window
Product: Core → Mozilla Application Suite
Comment on attachment 206206 [details] [diff] [review] Patch (untested, but should work) - Checked in trunk & branch 1.8/1.8.0 We will want this in branch too for final once it has an sr from someone like bienvenu
Attachment #206206 -
Flags: review?(iann_bugzilla)
Attachment #206206 -
Flags: review+
Attachment #206206 -
Flags: approval-seamonkey1.0?
Assignee | ||
Comment 5•19 years ago
|
||
I thought no sr is required for SeaMonkey only code (or do you as review offically request sr now ;)?
We still do r and sr in SeaMonkey code, for the moment.
Flags: blocking-seamonkey1.0?
Assignee | ||
Comment 7•19 years ago
|
||
Comment on attachment 206206 [details] [diff] [review] Patch (untested, but should work) - Checked in trunk & branch 1.8/1.8.0 Easy regression fix
Attachment #206206 -
Flags: superreview?(bienvenu)
Updated•19 years ago
|
Attachment #206206 -
Flags: superreview?(bienvenu) → superreview+
Comment 8•19 years ago
|
||
Comment on attachment 206206 [details] [diff] [review] Patch (untested, but should work) - Checked in trunk & branch 1.8/1.8.0 a=biesi
Updated•19 years ago
|
Flags: blocking-seamonkey1.0? → blocking-seamonkey1.0+
Comment 9•19 years ago
|
||
Checking in mailnews/compose/resources/content/MsgComposeCommands.js; /cvsroot/mozilla/mailnews/compose/resources/content/MsgComposeCommands.js,v <-- MsgComposeCommands.js new revision: 1.375; previous revision: 1.374 done
Keywords: regression
Version: unspecified → Trunk
Comment 10•19 years ago
|
||
Comment on attachment 206206 [details] [diff] [review] Patch (untested, but should work) - Checked in trunk & branch 1.8/1.8.0 2nd a=me
Attachment #206206 -
Flags: approval-seamonkey1.0? → approval-seamonkey1.0+
Comment 11•19 years ago
|
||
Comment on attachment 206206 [details] [diff] [review] Patch (untested, but should work) - Checked in trunk & branch 1.8/1.8.0 Checking in branch 1.8 MsgComposeCommands.js; new revision: 1.369.2.2; previous revision: 1.369.2.1 done Checking in branch 1.8.0 MsgComposeCommands.js; new revision: 1.369.2.1.4.1; previous revision: 1.369.2.1 done
Attachment #206206 -
Attachment description: Patch (untested, but should work) → Patch (untested, but should work) - Checked in trunk & branch 1.8/1.8.0
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Keywords: fixed1.8
Resolution: --- → FIXED
Whiteboard: fixed-seamonkey1.0
Updated•18 years ago
|
Keywords: fixed1.8.0.1
Updated•18 years ago
|
Keywords: fixed-seamonkey1.0
Whiteboard: fixed-seamonkey1.0
Comment 12•18 years ago
|
||
we're using "fixed1.8.1" for the 1.8 branch post-1.8 (confusing, I know)
Keywords: fixed1.8 → fixed1.8.1
You need to log in
before you can comment on or make changes to this bug.
Description
•