Closed Bug 195180 Opened 22 years ago Closed 22 years ago

Spurious copy of Composer window remains after sending email

Categories

(SeaMonkey :: Composer, defect)

x86
BeOS
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 187286

People

(Reporter: darenw, Unassigned)

Details

User-Agent: Mozilla/5.0 (BeOS; U; BeOS BePC; en-US; rv:1.3b) Gecko/20030112 Build Identifier: Mozilla/5.0 (BeOS; U; BeOS BePC; en-US; rv:1.3b) Gecko/20030112 When i click on a mailto: link on any web page, a Composer pops up -- good! But after I write my message and click the Send button, a flaky duplicate window remains behind. It never becomes active - its border remains the inactive color. Its widgets never get focus or function. The close button does not work. Oddly, the menu does work, and the Send and other buttons depress, but such events tend to remove focus (or in some way make disfunctional) other Mozilla windows, but this problem goes away easily if click in or tab key in those other windows in the 'right' combination. Otherwise, all other Mozilla windows continue to act normally, and further composer windows may be opened w/o problem except for making more flaky duplicates. Problem does not impede productive work with Mozilla. Reproducible: Always Steps to Reproduce: 1. Open any html file with a mailto: link 2. click it 3. write any message, with subject and to: filled in 4. Send it 5. Examine windows on desktop - you'll find a doppleganger! Actual Results: Spurious duplicate window remains where original composer window had been Expected Results: Composer window should disappear after Send button is clicked and mail protocol mechanism has done it bit flinging, leaving no residue anywhere on the desktop Havent' tried opening an email composer with the menu or starting up Mozilla with only a composer window; suspect same result
*** This bug has been marked as a duplicate of 187286 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.