Problem with tree in Vaadin 6.4.0

Vaadin 6 / 7 / 8 Framework UI
1

Hi,

I have a problem with the Tree component since Vaadin 6.4.0. :frowning:

When first shown, the top node seems to be missing, but with Firebug I’ve determined that it’s present, but out of the visible range on top. When clicked on a node, the tree shows correctly. When hitting F5 in the browser, the top node is again out of range.

The problem occurs in FF 3.6. In IE 7 & 8 it’s fine.

When reverting back to Vaadin 6.3.x => no problems

Switching the theme back to reindeer doesn’t solve the problem.

Someone have a clue ?

Thx

2

Hi,

Sounds quite bad. I tried to reproduce the issue, but without success. Do you have some code that I could use to reproduce the issue?

cheers,
matti

3

Hi,

I’ve created some code from the application. It was quiet difficult because we extend Tree to WefTree to do our own databinding in our own framework.


import com.essers.framework.wap.ui.WefTree;
import com.vaadin.ui.Label;
import com.vaadin.ui.Panel;
import com.vaadin.ui.VerticalLayout;

public class MainPanel extends Panel {

	public MainPanel() {
		
		VerticalLayout layout = new VerticalLayout();

                // WefTree extends Tree
		WefTree tree = new WefTree(TREE_DATATABLENAME);
		tree.setKeyColumns(new String[] {KEY_COLUMNNAME});
		tree.setParentColumns(new String[] {PARENT_COLUMNNAME});
		tree.setLeafColumn(LEAF_COLUMNNAME);
		tree.setDescriptionColumn(DESCRIPTION_COLUMNNAME);
		tree.setSizeFull();
		
		Label lbl = new Label("Label");
		layout.addComponent(lbl);

		layout.addComponent(tree);

		layout.setSizeFull();
		
		setContent(layout);
	}
}
4

Hi,

As you can guess the given code does not help me that much. I tried to reproduce the issue with following code snippet, but without any success. We are going to build 6.4.1 quite soon, so I’d like to resolve the issue soon.



    @Override
    public void init() {
        VerticalLayout content = new VerticalLayout();
        final Window mainWindow = new Window("TestApp", content);
        setMainWindow(mainWindow);

        content.setSizeFull();
        content.addComponent(new Label("Foobar"));

        Tree t = new Tree("Tree caption");
        t.addItem("Foo");
        t.addItem("Bar");
        t.addItem("Child");
        t.setParent("Child", "Foo");
        t.setSizeFull();
        content.addComponent(t);
    }

cheers,
matti

5

Hi Matti,

I’m not sure if it’s an Vaadin-issue or an issue of our own, but I’ve tried almost everything to fix the problem in my application.

The hard thing is because it’s embedded in our framework to get to the issue.

I’ll keep searching for a solution.

Can it be of any help if I provide you with the generated HTML copied from FIrebug ?

Thx for helping me out.

6

I’d guess not that much. There is so much magic happening behind the scenes that a static view of DOM is not enough. Try to reduce the test case from your application by slowly removing features and dependencies. I takes some time, but once you have the test case, somebody will probably fix the issue sooner more than later.

cheers,
matti

7

Hi Matti,

I’ve compared the generated HTML off the good layout with the HTML off the bad layout and they’re completely equal. :blink:

So I guess it’s a FireFox 3.6 problem. FireFox 4.0 beta doesn’t seem to have the problem. Older versions of FireFox are not tested

Thanks for your help.