When Region Pack is chosen, sidebars should be merged. Jaime to give further spec, if needed.

Is "Sidebar" the only UI that we wanna merge? Please have spec ready before handing over to developing team. I'll stay on CC' list; feel free to get me into brainstorming meeting.

typo: "developing team" should read as "development team".

Hi, Jaime: Would you run this with UE group to get a consensus first before we head off for implementation? For example, 1. Is there a limitation of the number of vendor channels can come from the global install directory? 2. Do we allow users to remove or reorder these vendor channels? 3. what's user experience of this? The answer might determine the complexity and difficulty of the implementation. We are very close to 0.9.4 freeze ....

Isn't this a duplicate of a bug that already open.

*** This bug has been marked as a duplicate of 77564 ***

I don't think this is a duplicate of bug 77564. That one would be satisfied if developers could simply add a panel to the existing user copy of panels.rdf -- it would essentially be calling the existing addPanel() code, only from within an XPInstall script and avoiding the block on chrome: URLs etc. *this* bug has to do with merging a global panels file, which might get updated, with the user's locally installed panels. Completely different areas of code and more work than the other one. Even if you implement this 'merging' issue there will still be a need for users to be able to install panels into their profile, and that's what bug 77564 is about.

--> trudelle QA --> claudius Assigning this a P2 | Major per lyecies recommendation.

-->sidebar QA

Changing component to Sidebar.

Make sure you are careful with this bug. There are several ways to solve this problem but some methods are going to lock you in and be a lot less fexible and more complex then you want. I commented about that in the meeting had. You can install a panel anywhere on the hard drive. If it is chrome of course it will have priviliges. So at this point we (shall i say you) can have panels in a region pack since it is part of chrome. In bug 77564 syd outlines what he proposal that is similiar and i commented that there are problems with profiles going down that route. Also note that there are similiar things going on with netscape.com and the sidebar. Privacy issues and granting privliges to tabs. All this work is going to either make that stuff harder or easier.

->sgehani

Let's push this one out to TM0.9.5, for now, and try to get it in early in the cycle. Samir/Peter - Do you want to nsbranch+ this one?

Based on discussions with Dan and Tao there are several outstanding issues warranting some rearchitecture of where the sidebar reads "panel lists" from, and how it decides to compose the panels displayed to users. 1) Installable panels: using XPInstall (separate bug 77564) 2) Optional component panels: move from monolithic -> modular panels datasources 3) Dynamic addition and removal of panels 4) Localized panels: switching collections of panels when locales switch The risk involved calls for this work to be moved to the next milestone to allow for adequate testing. Concurring with Jaime and moving to 0.9.5 for now.

Marking nsbranch- as it was decided in the August bug triage that we wouldn't have eenough time in eMojo to fix this. Let's revisit for MachV.

removing vestigial nsbranch keyword, ->0.9.6

Posted a proposal (still under construction) at: <http://mozilla.org/xpapps/sidebar/proposals/dyn-list.html> Once this proposal is complete I will contact key parties, incorporate their feedback, and then use this bug to track the various issues.

Moving to mozilla0.9.7.

[dyn-list] bugs -> mozilla0.9.8

what are the chances this is gonna make 098?

Sidebar triage team: nsbeta1-

-> Future

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

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

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

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

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

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

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

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

Useful, though rare, usually.