I have a multi-tab application with grids in tabs 1 and 2. In tab two, we initially load the grid with data on launch and have no issues with the vertical scrollbar being
displayed when we have data beyond the visible boundary of the grid.
However, this is not the case in the web data grid in tab 1. It is initially empty and we add data to the table by initially getting a datatable and then we merge to the existing datable and binding. Only difference is that when we reach the visible border of the grid, no scrollbar appears.
The webdatagrids are defined exactly the same in both tabs.
Idea's/Thoughts/Solutions???
Paul
Hey Pavel,
Thank you for contacting us and for the detailed explanation!
May I ask you some question related to Grid's configuration and used product version, for example could you please share with me if you are using BatchUpdating for example, are you adding the rows only on the client without commit to the server and respectively databind? Also are you using virtual scrolling or load on demand featured of the Grid, in general providing a code snippet with your Grid configuration would be very helpful, or better a sample that is showing the issue.
As for my thoughts, since this is not a known issue for us and I don't know how your Grid is configured, my suggestion is to have a look at your height attribute, for example a lot of issues are related to percentage boundaries and parent elements which don't have correct boundaries. Also, issues may appear when using Virtualization and Load on Demand. Also about the parent element (WebTab) could you please let me know if there is something in particular that I should know about it.
Could you please also share with me your exact product version?
Looking forward for your reply!
Controls version: 15.2.20152.2042
Height is calculated through javascript whenever the control is resized and on initial load. It is not set to a percentage. Columns are auto-generated.
This is my grid definition:
<ig:WebDataGrid ID="dgView" runat="server" Width="100%" StyleSetName="LucidDream" OnInit="dgView_Init" Visible="true" EnableAjax="False" EnableViewState="false" OnInitializeRow="dgView_InitializeRow">
<EditorProviders>
<ig:DropDownProvider ID="ddlViewValues" EditorControl-Width="50px">
<EditorControl runat="server" ID="ViewDropDown" ClientIDMode="Predictable" DropDownContainerMaxHeight="200px" DropDownContainerWidth="50px" EnableAnimations="False" EnableDropDownAsChild="False" DisplayMode="DropDownList" TextField="ViewValues" EnableCustomValues="False">
<Items>
<ig:DropDownItem Selected="False" Text="V" Value="V">
</ig:DropDownItem>
<ig:DropDownItem Selected="False" Text="C" Value="C">
<ig:DropDownItem Selected="False" Text="L" Value="L">
<ig:DropDownItem Selected="False" Text="X" Value="X">
<ig:DropDownItem Selected="False" Text="W" Value="W">
<ig:DropDownItem Selected="False" Text="-" Value="-">
</Items>
<DropDownItemBinding ValueField="ViewValues" TextField="ViewValues" />
</EditorControl>
</ig:DropDownProvider>
</EditorProviders>
<ClientEvents Initialize="dgView_Grid_Initialize" />
<Behaviors>
<ig:VirtualScrolling Enabled="False"></ig:VirtualScrolling>
</Behaviors>
</ig:WebDataGrid>
Hello,
What about the browser that you are using, WebTab definition and the js function which is manipulating the height? It would be highly appreciated if you could share this information with me. If you are afraid about the privacy of your code I've created a private case for you in order to communicate there (CAS-170086-T0W2F5).
Also I have created isolated sample base on your explanation and Grid definition, so could you please let me know what else should be added in order to invoke the issue?
Looking forward to hearing from you.
Will try to get to this when the weekend is over....regards.
Okay Paul,
Looking forward for your reply.
Turns out that having a missing "Height" attribute prevents the scrollbar from showing up. When I set an arbitrary height, despite Javascript changing it when it is rendered, the scrollbar shows up when more data is displayed on the screen.
I am verifying this as the answer. I don't know if this is therefore a bug on the infragistics side or not, but figured I would let you know the outcome.