Buddy List Panel should be served locally, not from netcenter

VERIFIED FIXED in M14

Status

SeaMonkey
Sidebar
P2
normal
VERIFIED FIXED
18 years ago
13 years ago

People

(Reporter: Paul MacQuiddy, Assigned: Steve Lamm)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [PDT+] will verify with 3/9 builds)

(Reporter)

Description

18 years ago
The buddy list panel is currently being served from Netcenter. This is probably 
bad, since it requires a slew of files to already be installed on the client, 
and Netcenter has no way of knowing this. Currently people with mozilla builds 
can try to add the buddy list, with less than optimal results :-)   You can also 
choose not to install IM with commercial build.

Plus, for some unknown reason, adding it from the Netcenter panel list doesn't 
work, so once you remove your buddy list you can't get it back.

Slamm says it is an easy fix to serve it up locally (like search, bookmarks, 
what's related), and johng has approved, marking beta1

Johng also has promised to have netcenter folk remove the buddy list from their 
server.
(Reporter)

Updated

18 years ago
Keywords: beta1

Comment 1

18 years ago
[PDT+] w/b minus on 3/8
Whiteboard: [PDT+] w/b minus on 3/8

Updated

18 years ago
Priority: P3 → P2
Target Milestone: M14
(Assignee)

Updated

18 years ago
Whiteboard: [PDT+] w/b minus on 3/8 → [PDT+] w/b minus on 3/8. Fix ready waiting for approval.
(Assignee)

Comment 2

18 years ago
Fixed.
Until Netcenter removes the local panels from their list, you will see
duplicates in the customize dialog.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Whiteboard: [PDT+] w/b minus on 3/8. Fix ready waiting for approval. → [PDT+] Fixed.
(Reporter)

Updated

18 years ago
Whiteboard: [PDT+] Fixed. → [PDT+] will verify with 3/9 builds
(Reporter)

Comment 3

18 years ago
verified, plus netcenter has updated their files to remove the local panels so 
no more conflicts
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.