I have the following settings on my igGrid:
When I resize my browser window, the columns holding the data resize automatically to fit the width of the page, however the header columns don't. I end up with this:
Is this a bug that has been fixed in the upcoming service release or am I doing something wrong with my settings?
Hi,
Having width 100% for the grid and a fixed pixel defaultColumnWidth for the columns is not applicable/supported together. If you have width 100 % defined, basically you shouldn't have any fixed column width set, as it will not have any effect and will lead to side effects as the one described. Default column width basically means a fixed, same width, applied on all columns - which doesn't change whether you resize the browser or not. You can define percentage width individually for any column, and it will play nicely with 100 % on the grid, while you're resizing the browser. So you can have 10%, 20%, etc. defined individually for any column (just as an example).
Let me know if this helps. Thanks,
Angel
Hi again,
just to clarify, above i was referring to the case when no column has a specific width applied, and you are only setting "defaultColumnWidth" in px. If you have some columns with percentage width defined, and some columns don't have any width set, and at the same time you have defaultColumnWidth in px, and percentage width for the grid, this combination will work fine. It will just make the columns that don't have width be 100 px, and then only the other percentage columns will resize when the grid resizes. I suppose that's what you are probably trying to achieve?
Thank you, Angel
That would be great Nikifor, I think it would be a handy feature to have for everyone who has variable column grids.
Hello,I have sent your feature request directly to our product management team. Our product team chooses new feature requests for development based on popular feedback from our customer base. Infragistics continues to monitor application development for all of our products, so as trends appear in requested features, we can plan accordingly.
We value your input, and our philosophy is to enhance our toolset based on customer feedback. If your feature is chosen for development, you will be notified at that time. Your reference number for this feature request is FR13572.
If you would like to follow up on your feature request at a later point, you may contact Developer Support management via email. Please include the reference number of your feature request in the subject and body of your email message. You can reach Developer Support management through the following email address: dsmanager@infragistics.com
Thank you for your request.
I've been thinking more about this problem and I believe that it is a bug fix I need and not a feature request.
No matter what my settings are, why is it that the data cells of columns will resize when the browser window is resized, and the fixed headers don't? Should this not be the default behaviour of the grid? I can't think of any scenario where you would want the current behaviour.
I have the same problem with header columns not aligning to data columns.
It is interesting to note that this only happens in Firefox (tested on 5.0.1).
My scenario is a grid with a few columns, with each column a fixed width in pixels.
The grid has a width larger than the sum of all columns: this I do setting it to 100%.
When stretching the FF browser window, header columns remain the fixed width and data columns stretch together with the window. :(
When stretching the IE browser window, header and data columns stretch together with the window (OK).
Hello,Please take a look at the attached sample created and tested via version 11.1.20111.1014. It was tested under FF 5,7 and IE 9 and provided no missbehavior like described from you. Please take a look at the sample and modify it if needed in order to reproduce the behavior you are facing. The grid contains 3 colimns with 200px width and the width of the grid is set to 100%
I'm afraid I can't test that. However I've noticed in your sample there is no filtering.
My test scenario without filtering behaves as expected, so maybe you can replicate the problem if you add filtering to your sample?