Closed Bug 218714 Opened 21 years ago Closed 15 years ago

Explore adding instant messaging hooks

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: mscott, Unassigned)

References

Details

We could help make thunderbird and mozilla mail act more like a PIM client by better integrating with existing (not built in) instant messaging clients. For instance, we can show IM presence in the message pane for email recipients for AOL screen names by running an http url with the email address in it. If other IM clients supported a similar technique, we could leverage that. Same goes for clicking on presence state in the message pane. If the user has an IM client installed and it properly registers as a url procotocol handler for it (such as aim urls with the AOL client), we could allow presence clicks to launch urls in the OS for the instant messaging client.
Blocks: 214223
Depends on: 223499
Scott, can we dup this to bug 216214? I think it's become the same thing, unless I misunderstand your comment.
Product: Browser → Seamonkey
Assignee: mscott → nobody
QA Contact: esther → message-display
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
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.