188754 - Mail notification (biff) text should be customizable

Status: NEW

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Benedikt Kantus]

I believe it a good idea what I heard today in the newsgroup: The biff text
should be customizable. Then people could use their own notification messages like:

"Hey! There were <x> people sending you email!"

Since there is only one variable in this text, it would be too difficult. A
single preference in user.js could do it.

Comment 1

[Benedikt Kantus]

Sorry, I meant: I would _not_ be too difficult.

Comment 2

[davidrmurray]

And people should be able to have an image pop up along with the text and the sound notification.

As Mark Bokil said on the NG today:

I like the idea. It would be cool if you could point the biff alert at 
an html file, jar or xml file and have it skinned appropriately. I would 
love to have a Homer rising up and down yelling out, "Doh!, more junk mail!"

Comment 3

[Benedikt Kantus]

I think it's better to do this in two steps. The first thing to do would be to
make the text customizable, which could be done by a simple preference, similar
the preference for the Reply-text.

After that we can start thinking about HTML or whatever.

Comment 4

[Jason Lefkowitz]

I second this.  What would be REALLY interesting would be if you could assign
text/sound/whatever to individual senders -- so if I get mail from my friend I
hear "Hooray", if I get mail from my boss I hear "d'oh!", etc.

Comment 5

[Benedikt Kantus]

*** Bug 214736 has been marked as a duplicate of this bug. ***

Comment 6

[Benedikt Kantus]

*** Bug 222081 has been marked as a duplicate of this bug. ***

Comment 7

[Benedikt Kantus]

Scott, this bug was assigned to your netscape.com address. Are you still the
right person to do this or should it be reassigned to someone else?

Comment 8

[Patrick]

(In reply to comment #0)
> Since there is only one variable in this text, it would be too difficult. A
> single preference in user.js could do it.

And what if you get mail on multiple accounts? Then there would be multiple
variables?

Comment 9

[Benedikt Kantus]

Well, so far I have never seen that biff shows several account names. I don't
actually know how that code works, but at least Thunderbird only shows me one
account name.

Comment 10

[Patrick]

(In reply to comment #9)
> Well, so far I have never seen that biff shows several account names. I don't
> actually know how that code works, but at least Thunderbird only shows me one
> account name.

I think there are several bugs open on separating biff by account. The quickest
one [remotely dealing with that] i could find is bug 247096, but i guess bug
145982 really deals with multiple notifications.

Anyway, my remark is just to meant to keep in mind that in the future it may be
more than just _one_ variable :)

Comment 11

[Robert Kaiser]

MASS-CHANGE:
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 12

[Robert Kaiser]

MASS-CHANGE:
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 13

[Robert Kaiser]

MASS-CHANGE:
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

[Xanthor Sccas]

This is a RFE, so it's still valid.