192261 - Attachments window in composing window doesn't scroll horizontally to display long filenames

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Michael T. Babcock]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130

If I attach a filename that is longer than the width of the attachment window, I
can't see the entire filename and there's no way to see it all without resizing
the entire composing window (and sometimes that's not good enough either).

Reproducible: Always

Steps to Reproduce:
1. Compose new message
2. Attach file with very long filename

Actual Results:  
The beginning of the filename/path displays, up to the width of the sub-window.

Expected Results:  
A horizontal scrollbar should have appeared at the bottom of the window in
question to allow me to read the entire attachment name.

Even though one would assume one knows what files they've attached, when you're
attaching two or more files and want to check which ones are already in the
list, its very difficult when you can't even read the filenames.

This may be related in UI to bug 145019 but I'm not sure.

Comment 1

[Ninoschka Baca]

A tooltip should help this problem (bug# 174697).

Comment 2

[Michael T. Babcock]

It may, but scrolling fixes more cases than a tooltip does, and scrollbars are
recognized functionality (people don't often wait for a tooltip to appear).

Comment 3

[Mike Cowperthwaite]

I suspect comment 1 meant bug 74697 rather than the one cited; that is actually 
an enhancement to the implementation of the tip in bug 47362, which has been in 
place for a long time.

Comment 4

[Gervase Markham [:gerv]]

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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

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.