Legend becomes garbled when expanded/collapsed

[chrisclaydon]

This is a little tricky to reproduce, but happens consistently. Paul Spencer has been able to reproduce it too.

Start with the Sheboygan sample data Sheboygan map. Using MG Studio, move the layers from the Base Map group into the root folder. Then create a layout that references the map and preview it in IE7.

Right-click on any layer in the legend, and select "Collapse All".

The legend becomes garbled until it is resized, or a zoom in/out of the map causes it to update.

[madair]

to date I've found that this is a problem when the ShowRootFolder extension is false and there are layers at the the top level of the tree (the tree view gets messed up in FF as well in that case) - no solution yet.

[chrisclaydon]

The problem seems to show up in IE when a layer group is empty in the tree view. This happens when it has no layers that are visible at the current scale. If I add several empty groups, it seems to be only the first one that is rendered in the wrong place.

[madair]

(In [1774]) closes #192: change to just call folder expand/collapse without re-arranging nodes in the expandAll/collapseAll operation

[chrisclaydon]

Even with the change made in submission 1774, when I first open a layout based on the Sheboygan sample map, the Transportation layer appears in the wrong place (see attached screenshot). Repeated zooming in and out can also still cause the legend to become garbled. So it doesn't appear to fix the problem.

A dotted line up to the top of the legend, a small piece of the label from the "hidden" root folder, and sometimes the highlighting from the root node itself are also visible...

[madair]

I'm having trouble reproducing this consistently now, however i did see it occur once. A solution that I would like to see tested in your environment is to add "overflow:hidden" to the ".jxTree li,.jxTreeRoot li" selector in the template CSS. I added that to slate/jxtheme.css and haven't seen the problem since in that template and that solution also solved a very similar issue in another project. If this solves the problem, the fix would have to go into the CSS for the templates.

[chrisclaydon]

The CSS change does seem to fix the problem.

[pagameba]

with the recent restructuring of the legend HTML and CSS from #227, this does seem to work again/still.