Community
Participate
Working Groups
treetable.js originally evolved as a component that can manage a tabular view of data. It used HTML table elements for its DOM. At some point, the ability to describe the elements that should be used was added. this._tableElement = options.tableElement || "table"; //$NON-NLS-0$ this._tableBodyElement = options.tableBodyElement || "tbody"; //$NON-NLS-0$ this._tableRowElement = options.tableRowElement || "tr"; //$NON-NLS-0$ I'm guessing that there were styling challenges, etc. with tables and that a move to divs simplified things for certain cases. If we ever start to support treetable as a consumable component outside of Orion, we might want to consider keeping the treetable representation internal (always divs?) rather than exposing this level of customization. Not sure.
A better approach might be to have the creator set a template for the "outer layer" of explorers and then template the rows. This gives the same level of control as we have now but in a more "typical" way. ie...if the client cares about the DOM structure underneath they should own it vs. setting some flags that "sort of" control it.
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html
