Attachments cannot be viewed in certain "Long String" situations (see bug 91662)



16 years ago
13 years ago


(Reporter: bwheadley, Unassigned)



Firefox Tracking Flags

(Not tracked)



(1 attachment)



16 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130

As an affect of resolution to bug 91662 (long strings), if the size of an
attachment forces Moz to resize the attachment box, the message area, or the
folders area, the name of the attachment does not appear in the attachment box.

Solution: The user must exit Mozilla. Upon restarting, displaying the same
message in the mail browser frequently will display the textual name of the
attachment. (Infrequently, but does happen, it will not. In which case you exit
Mozilla again and again until it works) Once the attachment's name is visible,
you can highlight it, and right-click to Open, Save or Save-As.

Reproducible: Sometimes

Steps to Reproduce:
1. It seems to be related to whether the Long String patch is executed, and
there is an attachment, and the length of the attachment's name is itself a long
string. I.E., it happens, and you don't know why. You restart, and it works.
Something is not being re-initialized between mail messages viewed.

Expected Results:  
Okay. The attachment's name is deemed "long". Instead of resizing the attachment
box so it's completely viewable, it should recognize that it needs a horizontal
scrollbar, and quit trying to resize the message area, and the message folder area.

Have a screenshot; will attach with bug.

Comment 1

16 years ago
Created attachment 108508 [details]
Screenshot of the Mail Client


16 years ago
QA Contact: olgam → gchan
Product: Browser → Seamonkey


14 years ago
Assignee: sspitzer → mail
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.