Thanks for the reply. I was only using it for row coloring. You're absolutely right about the overhead, it did seem a little weird considering how quick I found a workaround once I was "forced" to.
For anyone who's interested:
In the getHTML function of Mif.Tree.Draw, where the html.push is being written, I added this snippet into the wrapper span (Around line 680):
'<span class="mif-tree-background"></span>',
Then I added CSS rules:
.mif-tree-background {
width: 100%;
position: absolute;
left: 0;
z-index: -1;
height: 14px;
}
.mif-tree-node-wrapper:hover .mif-tree-background { background-color: #f0f0f0 !important; }
.mif-tree-node-selected .mif-tree-background { background-color: #e6e6e6 !important; }
.mif-tree-node-selected.mif-tree-node-wrapper:hover .mif-tree-background { background-color: #d9d9d9 !important; }
I've only been using it for a day, so it's far from perfect, but it was the solution I needed.
Keep up the good work!