Sent mail through web, the ok button to continue is darkened.



14 years ago
13 years ago


(Reporter: Aaron S, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)




(1 attachment, 1 obsolete attachment)



14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040421
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040421

I went to check AOL webmail through Mozilla. I can read, write, etc no problem.
When sending though, as the mail is sent and the confirmation window pops up to
say "your mail has been sent". the OK button can not be clicked, this window
appears to be embedded into the window below it which was the email window. It
isnt a show stopper, since you can just click the X button to get out of it. 

Reproducible: Always
Steps to Reproduce:
1.Log into AOL webmail.
2. Create or reply to a mail and hit send.
3. This window with the confirmation is where the problem is.

Expected Results:  
Should be able to click the ok button to close the email.

Comment 1

14 years ago
Created attachment 147087 [details]
Screen capture of issue.


14 years ago
Attachment #147087 - Attachment mime type: text/plain → image/png

Comment 2

14 years ago
Created attachment 147202 [details]
fixed WebMail.png

The other attachment had been corrupted.


14 years ago
Attachment #147087 - Attachment is obsolete: true

Comment 3

14 years ago
Do you get anything in the Javascript console(Tools -> Web Development)?  You
might have to clear it first.  The confirmation window looks like it is part of
the website and not a native confirmation box.
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.