Community
Participate
Working Groups
The Tree can do pretty much everything the Table can. Using the same client-implementation for both would make the client thinner and more easily maintanable. It would automatically fix this bug: Bug 241924 - [table] Selection using shift and cursor keys not possible It MIGHT also automatically fix these bugs: Bug 326941 - [Table] js-error "item is undefined" when setting visibility false Bug 311837 - [Table] Hover state not reset on mouseout Bug 324759 - [Table] Content cut off 1px at the bottom Bug 315426 - Table gridlines missing in IE upon view tab selection Bug 276051 - [Table] Wrong selection behavior with Shift-click on empty selection Bug 306377 - [Table] Selection occasionally doubled when scrolling fast Bug 234103 - [Table] #showItem() does not work when called before Shell bounds are set It might also help fix these bugs: Bug 233614 - [Table] Column texts initially truncated Bug 311169 - [Table] Support Gradient for TableItem Bug 313291 - [Table] slow relayouting when the visible area is large
*** Bug 335169 has been marked as a duplicate of this bug. ***
Just speculating, but List could also (at one point) be merged into this. List itself is rather small, but is the only widget to use the relatively big SelectionManager.js. On the other hand, this would also mean List would use virtual scrolling, which is not as smooth as the current "real" scrolling.
Commited some preparations into CVS HEAD. Basically i created a new Widget from Tree called TreeRowContainer, which will later be used in Table. Also some minor adjustment of the client Table API to make it more compatible with Tree.
Fixed in CVS HEAD. Old Table.js, TableItem.js and TableRow.js have been removed.