add per server ui (to the account manager) to control the "abbreviate" pref.

NEW
Unassigned

Status

SeaMonkey
MailNews: Account Configuration
18 years ago
9 years ago

People

(Reporter: (not reading, please use seth@sspitzer.org instead), Unassigned)

Tracking

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Comment 1

18 years ago
This is a joke, right? Please tell me this is a joke.
no, it's not a joke.  we have the per server "abbreviate" pref, and we should
eventually have a way for users to disable / enable it in the UI.

but it is pretty advanced, so perhaps it should be burried on some "advanced
prefs" dialog. (along with other advanced prefs not currently in the UI).

imap servers have an "Advanced..." button, news should have one two with this
type of thing.  an example of another pref that will eventually go there is
"push auth".

accepting.
Status: NEW → ASSIGNED

Updated

18 years ago
QA Contact: esther → nbaca

Comment 3

18 years ago
*** Bug 61795 has been marked as a duplicate of this bug. ***
Depends on: 63679

Comment 4

17 years ago
We had talked about this a long time ago, but it never happened.

http://www.mozilla.org/mailnews/specs/accounts/images/AcctServerNews1.gif

Maybe this does belong in an "Advanced" dialog.

Comment 5

16 years ago
*** Bug 134751 has been marked as a duplicate of this bug. ***

Comment 6

16 years ago
We have too many prefs in Mozilla and mailnews. In fact, we have so many of them
that we have bugs that are tracking the status for shrinking the amount - so
that they even fit into the panels. I am of the opinion that only the most
important preferences should be user-visible, more subtle details like this one
can very well be hidden, as most users will probably be satisfied with 1) the
tooltip that appears when you hover over a newsgroup in the folderpane, and 2)
the hidden option -- which most people won't use anyway, unless they are
extremely annoyed.

Please take away this preference from the spec; this (abbreviated vs.
non-abbreviated newsgroup names) is really a implementation decision that *we*
are supposed to make, not force upon the user to decide.  And even then, we have
the tooltips and the hidden preference. Needless to say, I vote for WONTFIX.

Comment 7

16 years ago
*** Bug 134751 has been marked as a duplicate of this bug. ***

Comment 8

16 years ago
*** Bug 148201 has been marked as a duplicate of this bug. ***

Updated

16 years ago
Blocks: 148346

Comment 9

16 years ago
*** Bug 162726 has been marked as a duplicate of this bug. ***
*** Bug 184896 has been marked as a duplicate of this bug. ***

Comment 11

16 years ago
When you're subscribed to maybe 200 newsgroups that you think you might be
interested in looking at sometime, it is ABSOLUTELY HELLISH TO FIGURE OUT WHAT
YOU'RE LOOKING AT IN THE NEWSGROUP LIST FOR A SERVER. DOWN WITH ABBREVIATIONS,
OR MAKE IT A USER CHOICE! THIS IS A CRITICAL USABILITY ISSUE.
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail
Status: ASSIGNED → NEW
Priority: P3 → --
QA Contact: nbaca

Comment 12

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 13

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 14

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 15

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 16

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 17

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 18

9 years ago
Still valid, possibly wontfix in the end...
Status: UNCONFIRMED → NEW
QA Contact: mailnews-account
Hardware: x86 → All

Comment 19

9 years ago
I'll leave it up to Mnyromyr as the MailNews owner to decide if this is WONTFIX or something we want to do.

Comment 20

9 years ago
Personally, I've never understood why we abbreviate the group names in the first place. 
Given the recent development of a JS implementation of the folder pane, which we will at some point port to SM as well, this might end up as extension fodder.

Leaving open until then for reconsideration.
You need to log in before you can comment on or make changes to this bug.