Closed Bug 169253 Opened 22 years ago Closed 14 years ago
move oscar / IM / AIM / YIM prefs for presence out of ab .js and into mailnews
move oscar / IM prefs for presence out of ab .js and into mailnews.js this will allow power users to configure things, like ICQ, irc, MSN messenger, YIM, etc.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.2beta
Or one day, add a picker menulist to prefs for: For instant messaging us [MSN, YIM, ICQ, irc, AIM, jabber] and we could set these hidden prefs appropriately. coolness.
not going to happen for 1.2 beta, sliding out.
Target Milestone: mozilla1.2beta → mozilla1.3alpha
if we use the oscar url for aim presence in the hdr area, we'd use the same pref.
for the oscar pref stuff (http:// urls), see: http://lxr.mozilla.org/mozilla/source/mailnews/addrbook/resources/content/abCard ViewOverlay.js#230 for the im pref stuff (goim: urls) see: http://lxr.mozilla.org/mozilla/source/mailnews/addrbook/resources/content/addres sbook.js#717 http://lxr.mozilla.org/mozilla/source/mailnews/addrbook/resources/content/abCard ViewOverlay.js#221
moving to 1.3 beta. by 1.3 final, we should be IM agnostic.
Target Milestone: mozilla1.3alpha → mozilla1.3beta
moving out, no plans to do this for 1.3, but I'd accept patches. this would be an easy bug for someone to do. just move code from hard coded to prefs.
Target Milestone: mozilla1.3beta → Future
another summary: clean up the integration with AIM so that YIM other IM clients can integrate with the addressbook and mail. make it an optional tbird install, like offline.
Summary: move oscar / IM prefs for presence out of ab .js and into mailnews.js → move oscar / IM / AIM / YIM prefs for presence out of ab .js and into mailnews.js
QA Contact: nbaca → addressbook
Target Milestone: Future → ---
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: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.