panes initially display less than full width

[Sheryl Landon]

The panes in our splitter initially display at a fraction of whole browser width, and then expand to full width as the page finishes loading.  It's a little distracting.  Is there a way to get the panes to display immediately full browser width?

Thanks,
Sheryl

[Svetlina Anati]

Hi Sheryl,

I assume that most probably the splitter's size in your case is set in percentages as well as that of the splitter's panes. If so, their sizes are calculated depending on the size of the browser window. If you do not want to observe the resizing process I could suggest you set the VisibleDuringInit property of the splitter to false in order to avoid the undesired effect which occurs while the page loads and the RadSplitter gets initialized.


Best wishes,
Svetlina
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.

[Peter]

Hi there,
I currently have the exact same issue. Everything within my splitter has a width and a height percentage. The splitter works great in that it fills the page, however during initial load the height and width is around 400x300 pixels. Is there a reason why Telerik uses javascript to resize the splitter for width? Maybe there's something I'm missing. The container element is a div with an inline style width:100%. I know height is another issue, however, width should be just fine leaving it to the inline styles.

[Tsvetie]

Hi Peter,
First of all, I would like to mention, that the RadSplitter is actually a table, not a DIV element - the element you refer to is just the wrapper element.

One of the main principles that we follow, when we develop our controls is to get consistent behavior under all supported browsers. As you probably know, that is not an easy task. There are various reasons why we have decided to keep the size of the elements in the RadSplitter in pixels. For example, the Scrolling functionality or the MinWidth/MinHeight and the MaxWidth/MaxHeight functionality of the RadPanes.

I agree that for simple scenarios, using css styles to set the Width of the RadSplitter in percents is a better approach, but unfortunately, this approach would prevents us from providing all the functionality that the controls currently offers.

All the best,
Tsvetie
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.

[Peter]

Thanks for your reply,
This makes more sense then. During my very small investigation I didn't realize it was a table that had a div element wrapper. At this point it's understandable to use javascript resizing.

It seems like what Svetlina had said makes the most sense for the user experience. I would also recommend using a loading panel in it's place when doing any sort of ajax functionality so the user isn't clicking around while there's a blank screen during the splitter load.

[Paul]

Hi,

I am also experiencing this issue. I have my splitter width and height set in percentages (100% to be exact) and when the page loads, it starts out small, then expands to the browser window width.

I tried using VisibleDuringInit as mentioned in this forum, but it appears to have no affect at all in IE. I have a nested splitter so I placed there as well. Nothing seems to make a difference. I did test it in FireFox and that appeared to behave perfectly. Unfortunately, the vast majority of the people who will be using the internal site I am building is IE6 & 7 so it needs to work in those browsers.

I am using Q2 2008, by the way.

Any ideas or workarounds?

Thanks!!!

Paul

Edit:

One observation I've discovered is that this appears to only affect the RadSplitter I have in my master page. I do have other RadSplitters (which load through a content placeholder in one of the RadPane's in the master) and they appear to behave as designed.

I did notice (and mentioned in another thread I started) that any nested RadSplitters nested through another created in the master page as in my situation seems to inherit the properties of the main splitter (such as bordersize).
I did not place VisibleDuringInit on any other splitters, but they all were affected because of how they load through the place holder on the master page's RadSplitter.

[Tsvetie]

Hello Paul,
You should set VisibleDuringInit to "false" for all RadSplitters on your page. The RadSplitters do not inherit properties from their parent RadSplitter (if any). Even though there are differences in the borders of nested RadSplitters and not-nested RadSplitters - those are by design. Most users do not expect to see double borders when they nest two splitters. That is why, we remove the borders of the child splitter.

Indeed, there were problems with the VisibleDuringInit property of the splitter, but they were fixed in the latest (Q2 2008) release. That is why in case you have any problems with this property, please prepare and send us a simple running project, demonstrating them.

Sincerely yours,
Tsvetie
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.