To whom it concerns:
I've recently encounted issues with the dynamically generated span's that are generated when you click on a grid header column to resize it (see in the telerik.web.ui source code GridColumnResizer.js, ~line 14 and GridCommon.js, ~line 644 for the one i'm referring to). The issues occur when the grid(s) in question exist inside of an absolutely positioned window that is then able to be scrolled (overflow-y:scroll being set on the content container within that window).. Since the auto generated spans are absolutely positioned based on the body element, it doesn't know that the grid it is supposed to sit on top may be scrolled out of the way. A couple suggested fixes would be to generate those spans relatively positioned within the immediate container to the grid. A quick fix would have been to give those spans a class so that we can just hide them, since they don't 100% work across browsers anyway (not for me at least).
I'd love to hear if there are other suggestions to that issue.
Thanks!
Seth Messer
I've recently encounted issues with the dynamically generated span's that are generated when you click on a grid header column to resize it (see in the telerik.web.ui source code GridColumnResizer.js, ~line 14 and GridCommon.js, ~line 644 for the one i'm referring to). The issues occur when the grid(s) in question exist inside of an absolutely positioned window that is then able to be scrolled (overflow-y:scroll being set on the content container within that window).. Since the auto generated spans are absolutely positioned based on the body element, it doesn't know that the grid it is supposed to sit on top may be scrolled out of the way. A couple suggested fixes would be to generate those spans relatively positioned within the immediate container to the grid. A quick fix would have been to give those spans a class so that we can just hide them, since they don't 100% work across browsers anyway (not for me at least).
I'd love to hear if there are other suggestions to that issue.
Thanks!
Seth Messer
1 Answer, 1 is accepted
0
Accepted
Hello Seth,
I am afraid this is a tough issue and cannot be easily fixed. We cannot position the <span> elements relatively to the RadGrid's parent, because this parent will need a relative position style and it is not a good idea for RadGrid to interfere with other web page elements' styles. The <span> cannot be descendants of the RadGrid <div> element either, because of an Internet Explorer bug, which will prevent them from being positioned correctly. In general, there are some problems in IE when relatively/absolutely positioned elements are used together with scrollable containers.
As for the CSS classes, the <span>s actually have ones:
.TopReorderIndicator_Skin
.BottomReorderIndicator_Skin
If you want to hide these two elements with CSS, you may need to use !important in order to override display and visibility styles set with Javascript.
In case you are using RadGrid Q2 2008 SP1 with ImagesPath, then the <span>s render differently and do not have CSS classes, but we have added such already and the change will take effect in our next release.
Sincerely yours,
Dimo
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
I am afraid this is a tough issue and cannot be easily fixed. We cannot position the <span> elements relatively to the RadGrid's parent, because this parent will need a relative position style and it is not a good idea for RadGrid to interfere with other web page elements' styles. The <span> cannot be descendants of the RadGrid <div> element either, because of an Internet Explorer bug, which will prevent them from being positioned correctly. In general, there are some problems in IE when relatively/absolutely positioned elements are used together with scrollable containers.
As for the CSS classes, the <span>s actually have ones:
.TopReorderIndicator_Skin
.BottomReorderIndicator_Skin
If you want to hide these two elements with CSS, you may need to use !important in order to override display and visibility styles set with Javascript.
In case you are using RadGrid Q2 2008 SP1 with ImagesPath, then the <span>s render differently and do not have CSS classes, but we have added such already and the change will take effect in our next release.
Sincerely yours,
Dimo
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.