View Full Version : [DEFER-482][2.x/3.x] TreePanel Node Highlight Problem

27 Jan 2009, 5:50 PM

Windows Vista
Firefox 3.02
Google Chrome
(possibly all browsers?)

What steps will reproduce the problem?

The ExtJS sample "Layout Browser" (http://www.extjs.com/deploy/dev/examples/layout-browser/layout-browser.html) exhibits the problem.

Drag the vertical layout split bar to the left so as to create a horizontal scroll bar in the TreePanel section.

Scroll this panel to the right (somewhere in the middle.. see attached).

Highlight or select any node

What is the expected output?

Highlight for selected item should extend to the width of the viewable area within the panel

What do you see instead?

The highlight for the selected node is truncated. The length of the highlight is consistent with the width of the panel when the horizontal scroll is "fully" left, but having the scroll bar moved to the right displays the truncated highlight.

See attached screenshot

27 Jan 2009, 10:35 PM
I've seen this before (https://www.extjs.com/forum/showthread.php?t=53763), but never made a bugreport for it.

My solution was:

.x-tree-root-ct {float: left;}

Animal's solution was:

div.x-tree-node-el {display: table-cell;}

(both work)

28 Jan 2009, 4:01 AM
Awesome man. I wasn't actually expecting a solution as it's a fairly minor issue, but it's great that you already knew about it.


26 Jan 2010, 2:33 AM
Still a problem in Ext 3.1.1-beta.

(details on side effects of this solution can be found here (http://www.extjs.com/forum/showthread.php?t=80296))

26 Jan 2010, 8:54 PM
It would be nice if this issue could be solved. :)

Jamie Avins
27 Jan 2010, 6:50 AM
It's on our radar, we're looking over this as there are side effects to Condor's solution.

19 Mar 2010, 7:28 PM
Any updates on this...maybe for 3.2?

Jamie Avins
22 Mar 2010, 8:09 AM
We took some time to review the issue. It isn't an easy fix and requires a full restructure of the dom structure currently used to generate a tree. To fix it in a script to shift css around dynamically (whether a scrollbar was present or not) would cause performance issues and just be too much of a hack. This is being deferred to a major revision when we can fix it properly.