Closed Bug 550525 Opened 12 years ago Closed 12 years ago

Composer dialog opened via "Send Link" (from SM bowser) will not send message

Categories

(SeaMonkey :: Composer, defect)

SeaMonkey 2.0 Branch
x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bleb2tie, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100205 Lightning/1.0b1 SeaMonkey/2.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100205 Lightning/1.0b1 SeaMonkey/2.0.3

In Seamonkey browser if I click File->Send Link a Seamonkey Compose dialog opens as expected with the From, Subject & Body fields pre filled as expected. After filling in a To recipient address, I click on the Send button and nothing happens & no errors are shown. 

A variant of this behaviour sometimes occurs and the Subject field is correctly filled with the webpage title but "greyed out/non-editable" and the Compose dialog title is "Compose: (no subject)". In this variant it is also not possible to fill in the recipient address.

In the same session if I open the full Seamonkey email client I can successfully compose and send a new message having cut & pasted the fields from the original non-functioning Compose dialog into the new Compose dialog.

Reproducible: Always

Steps to Reproduce:
1.Start Seamonkey browser
2.Open a webpage eg: http://www.mozilla.org/about/
3.File->Send Link
4.In Compose dialog enter a recipient address & attempt to send the message
Actual Results:  
Send button does nothing

Expected Results:  
Send button should send message

Running under Debian Lenny and xfce desktop
Default Seamonkey theme
Seamonkey has following extensions: 
Adblock Plus 1.1.3
British English Dictionary 1.1.9
ChatZilla 0.9.86 (disabled)
Display Mail User Agent 1.6.5
DOM Inspector 2.0.4
Enigmail 1.0.1
Flashblock 1.3.15
JavaScript Debugger 0.9.87.4
Lightning 1.0b1
Password Exporter 1.2 (disabled)
Sync Kolab 1.5.201002111138
User Agent Switcher 0.7.2
Virtual Identity 0.6.1
Version: unspecified → SeaMonkey 2.0 Branch
Please close: its not your bug. Disabling the Virtual Identity extension restores the expected behaviour. I'll take it up with the author of that extension.

Sorry to have wasted your time.
See Comment 1 -->> Worksforme
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.