In IE6 and FireFox the NavBar renders correctly and consistently.

In IE7, the first few first level nodes will render/expand correctly.. but the proceeding nodes will be rendered way down beneath my page.

The nodes that rendered down past the viewable area do not cause the page to scroll.. yet I can verify that they are there if I cause my page to scroll (a callback grid that extends past the fold).

I have seen this issue on Windows XP, Windows 2003 (32 and 64-bit) and Vista.

It has happened on a fresh install (no corporate policies applied) and locked down machines alike.

Some machines seem to reproduce the issue more than others.. but even the machines that see this strange behavior often (most of the time) occasionally will see it rendered correctly.

Is it possible that the area assigned to render the second level nodes is causing the rest of the nodes to be pushed down past the page?

This has been an issue we've had with ComponentArt since IE7 was released and I've been hoping a fix would make its way into your later releases but it has not. Has anyone seen anything like this before?

We don't have any known issues with NavBar in our latest release.
This might be related to the page latyout or other variables in your page.
Can you describe the layout and post your Navbar definition for us to look at?
Are you assigning the area to the second level manually? If yes, can you also post the code for that?

The NavBar sits within a table cell of height 400px. The NavBar definition is below: The code excerpts to populate the navbar: System.Data.DataSet ds = GetNavBarDataSet(); ComponentArt.Web.UI.NavBarItem newItem; ds.Relations.Add("NodeRelation", ds.Tables[0].Columns["NODE_ID"], ds.Tables[0].Columns["PARENT_ID"]); foreach (DataRow dbRow in ds.Tables[0].Rows) { if (dbRow.IsNull("PARENT_ID")) { //dbRow["Text"].ToString(), dbRow["ImageUrl"].ToString(), true); newItem = new ComponentArt.Web.UI.NavBarItem(); newItem.ID = "Item" + dbRow["NODE_ID"].ToString(); newItem.Text = dbRow["NODE_TEXT"].ToString(); newItem.DefaultSubItemLookId = NAVBAR_DefaultSubItemLookId; newItem.SubGroupCssClass = NAVBAR_SubGroupCssClass; newItem.SubGroupItemSpacing = NAVBAR_SubGroupItemSpacing; newItem.Expanded = false; nb.Items.Add(newItem); PopulateSubNavItem(profileID, dbRow, newItem); } } private static ComponentArt.Web.UI.NavBarItem PopulateSubNavItem(int ProfileID, DataRow dbRow, ComponentArt.Web.UI.NavBarItem nbItem) { foreach (DataRow childRow in dbRow.GetChildRows("NodeRelation")) { ComponentArt.Web.UI.NavBarItem childItem = CreateItem(ProfileID, childRow); nbItem.Items.Add(childItem); PopulateSubNavItem(ProfileID, childRow, childItem); } return null; } The problem is not the NavBarItems themselves, which are rendered – they are just no longer constrained by the limits of the NavBar itself. It is as if the generation code is miscalculating how high the NavBar is, and therefore when the first node is expanded, it expands too far and pushes the other beyond the boundaries of the NavBar. As it is difficult to reproduce, I cannot provide more information as to the resulting DOM structure of the NavBar. There are a number of other ComponentArt controls on the page, including Grids, CallBacks, and TreeViews, but I do not believe they are affecting the NavBar.

Any thoughts on how to fix my problem? If I cannot find a solution in a timely manner, I'll be forced to remove the ComponentArt NavBar component. I'm not horribly excited about this.. but as the options that the rendering issue are crucial, I need a solution that renders properly 100% of the time.

It is probably due to a layout issue, can you explain the layout or possibly post the container code and CSS.
Forum is mainly for peer-to-peer support as noted in the post/reply page. For guranteed and timely response please use our online support form
Someone will get back to you, and you can attach the related code to speed up the process.

Hi Chrisf,

Were you ever able to find a solution for this problem? I'd love to hear about it if you have.

I am experiencing the same problem you described of items in the NavBar being pushed out of the displayed NavBar area. I have multiple levels in my NavBar and when I expand items, they push off the last NavBar items outside of the displayed limits of my NavBar. When I collapse an item in level 2 that was expanded when its parent level item was initially expanded - I get white space at the end of my control. It is as if the height of the NavBar control does not adjust properly to the currently displayed (expanded/collapsed) items.

Occasionally this will work properly - and boy it is exactly how I'd like it to function. This problem (as well as the occasional working properly) occurs both on my live webserver (in a non-public sandbox area) and on my local machine.

As you described, I have a number of other ComponentArt controls on my page as well (including splitters, other navbars, toolbars, and menubars).

The one difference between the problem you described and mine is that for me this is problem in IE 7 as well as in Firefox (v2.x).

Any help you can provide based on your experience would be really appreciated!

Thanks,
Jen

Hi Jen,

I'm actually sorry to say that we never found a solution. As time went on and the number of customers experiencing the issue increased, we were forced to stop using the ComponentArt NavBar. As the NavBar is a fairly simple component, we opted to write out own version that looks and acts relatively the same.

We still use ComponentArt in many other parts of the product; the NavBar rendering issue was the first ComponentArt problem that we've been unable to solve.

Sorry I couldn't provide the answer you were looking for.

-Chris

Jen,

Are you able to submit a support request with your sample so we can try and debug it in house?

Cheers,

Was there any progress on this? I also encountered this issue.
It happens in Firefox and Safari too.

Hi Trevor,

Are you able to submit a support request so we can do a code share? Once you receive your confirmation email, reply with your attachment.

I'm sure we can figure this out, it most likely is mismatched CSS on the page.

Cheers,