Closed
Bug 752463
Opened 14 years ago
Closed 3 years ago
Tools > Options: Reposition "Attachments" tab to follow "Display" and "Composition"
Categories
(Thunderbird :: Preferences, enhancement)
Thunderbird
Preferences
Tracking
(Not tracked)
RESOLVED
INACTIVE
People
(Reporter: mstanke, Unassigned)
Details
Attachments
(1 file)
|
128.60 KB,
image/jpeg
|
Details |
I think Options deserve better order. E.g. "Attachments" might follow "Composition". Especially "Outgoing" tab is deeply related. In "Composition -> General" tab is also "Check for missing attachments" option. There really should be some connection between.
Component: Theme → Preferences
QA Contact: theme → preferences
Version: unspecified → Trunk
Comment 1•8 years ago
|
||
Michael, thanks for this RFE and sorry for late reply.
There's always different ways of arranging things. I think those tabs were arranged by order of relevance to the user, from basic to advanced. "Attachments" tab has some pretty advanced stuff which the average user will never need (but also some basic stuff like where to save attachments, unfortunately with UI failures so basically not working...)
So the current order isn't bad, but maybe we could move "Attachments" between "Composition" and "Chat" as user suggested.
In favor of that, the logical sequence | Display (mostly incoming) | Composition (mostly outgoing) | Attachments (incoming and outgoing) | does seem to make sense, those are core messaging-related settings, whereas the rest like Chat, Privacy, Security, and Advanced are arguably more and more peripheral.
Richard, what do you think?
Flags: needinfo?(richard.marti)
Updated•8 years ago
|
Summary: reorder Options cards (Attachments) → Tools > Options: Reposition "Attachments" tab to follow "Display" and "Composition"
Comment 2•8 years ago
|
||
There exists also chat protocols which can send receive files which depends on the attachments tab.
But moving this tab is okay as the main usage is in mail/news.
Flags: needinfo?(richard.marti)
Updated•4 years ago
|
Severity: normal → S3
| Reporter | ||
Updated•3 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•