Closed
Bug 535484
Opened 15 years ago
Closed 5 years ago
Recipients pane/area should auto-expand as needed (resize to show more rows for To:, CC:, BCC: addresses etc.)
Categories
(Thunderbird :: Message Compose Window, enhancement)
Thunderbird
Message Compose Window
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mlissner+bugzilla, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7pre) Gecko/20091212 Ubuntu/9.10 (karmic) Firefox/3.5.2
Build Identifier: 3.0
Not sure what this area is called, but the area where there are four spots to enter to whom an email is to should auto-expand when a message is being written to more than four people.
It should work like this:
1. The user puts in four recipients
2. They press enter to input another.
3. The area gets larger to accommodate the additional person.
4. Steps 2 and 3 repeat as needed.
5. They press tab to compose the subject of the message..
6. The area auto-compresses back to the normal four spots.
This would make the entry of lots of people more efficient because:
- you'd be able to see the names you already entered.
- it wouldn't scroll faster than you can see it scroll when you press enter.
Reproducible: Always
Updated•11 years ago
|
Comment 1•11 years ago
|
||
This was favourably considered in Bug 425451 Comment 22, but not implemented (yet).
But it's probably just another stop-gap until we normalize our recipients area per
Bug 440377: Move away from the one-line-per-recipient paradigm and do like most others do, multiple recipients on a single line.
Updated•11 years ago
|
Updated•11 years ago
|
Summary: The To: area should Auto-expand as needed → Recipients pane/area should auto-expand as needed (resize to show more rows for To:, CC:, BCC: addresses etc.)
Comment 2•5 years ago
|
||
Since bug 440377 landed, and the recipients area expands accordingly, this is a WORKSFORME
.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•