My igGrid always seems to render first time with the page item count dropdown open as per the attached image.
Any ideas as to why this is?
Hello duster,
Thank you for posting in our community.
In order to investigate this matter further I created a small sample using igGrid with paging. For my test I am using version 15.1, latest service release, which currently is 15.1.20151.2112. I am testing my sample in Internet Explorer 11, Chrome and Firefox and I was not able to reproduce the behavior that you are describing.
I am attaching my sample for your reference. Please test it and let me know how it behaves on your side. If this is not an accurate demonstration of what you are trying to achieve please feel free to modify it and send it back to me.
Also providing me some additional information such as IgniteUI version, browser, jQuery version and anything that you might consider related may help me in my further investigation.
Looking forward to hearing from you.
Hi Vasya
I am using version 2014.2 of IgniteUI. The behaviour happens in both Chrome and IE (the only two I have tested it in).
It also only happens the first time I load the page with the grid on it in a session - subsequent page loads work fine.
One thing I have noticed is that it seems to take the grid a long time (around 20 seconds) to load a very simple grid with only 10 or 12 records. The server side to get the grid model and data runs in 4ms.
This also is only the first time the page is loaded in a session. I have the IG css and script files locally too, so there should be no downloading going on.
The same behaviour happens to the page selection dropdown as per the attached image:
I have coded a workaround which sorts out the issue by catching the grid's rendered event on the client and forcing re-selection of the page size:
$("#gridResults").igGridPaging("pageSize", 5);
not ideal, but works for the moment.
.
Thank you for your clarifications.
I modified my sample to use version 14.2. Please try modifying my sample in order to reproduce this issue. This is going to be highly appreciated and will help me investigate and debug on my side in pursuit if the root cause for this matter.
I assume that this might be caused by some css classes being applied. If you are using any custom css or for example Bootstrap theme please include this the sample as well.
Please feel free to continue sending updates to this case at any time.