Places' tree view should work just like the toolbar and menu views: The PlacesTreeView object should become the.. places view for trees, rather than the custom tree binding we have. and it should then "manage" a standard xul tree (just as PlacesToolbar manages a standard toolbar element). There's no need for a custom binding. This isn't just a matter of code cleanup. The current confusing setup of treeView.js+tree.xml introduced quite a few regressions in the past, and some code duplication between the files.
One of the possible outcomes of bug 1446339 is that we will replace the current interface with something based on different code. We should probably only spend time on this particular bug if the plan changes or takes too much time.
Depends on: 1446339
You need to log in before you can comment on or make changes to this bug.