This topic lists the known issues and limitations in the 2011 Volume 2 release of the Ignite UI for jQuery™ library.
The following table summarizes the known issues and limitations of the Ignite UI for jQuery 2011 Volume 2 release. Detailed explanations of known issues and the possible workarounds are provided for in the known issues topics for each control.
 |
Workaround available |
 |
No known workaround |
 |
Fix planned |
| Feature | Description | Status |
|---|---|---|
| Using Document Engines from NetAdvantage for ASP.NET and Ignite UI for jQuery together workaround | Using both the Infragistics ASP.NET and Ignite UI for jQuery documents assemblies together will cause namespace conflict exceptions. | |
| igEditor styling | Layout of html elements was modified and rounded corners are rendered around whole editor, not only buttons. | |
igEditor spin buttons |
Spin buttons are rendered horizontally. | |
| igEditor rendering failure | Rendering may fail if the base element is TD. | |
| Cannot use igGridHiding with row templates | igGridHiding™ cannot hide columns when row templates are used. |
|
| igGridGroupBy and autoGenerateColumns to True prevents other columns from being grouped | If a grid control has some columns explicitly defined and autoGenerateColumns set to true, having columns grouped at initialization will prevent other columns from being grouped at runtime. |
|
| MVC helper configuration for flat grids | All grids are generated as igHierarchicalGrid™ by the MVC helper for grids. |
|
| Grid column widths | The scenario where some columns' widths are defined in percentage, while others' are in pixels (or not specified at all) is not supported. | |
| Grid layout problems for header and footer elements in Microsoft Internet Explorer® 7 | When grid width is not specified, header and footer elements are rendered shorter than the grid in Microsoft Internet Explorer® 7. | |
| Grid API calls do not work as expected with DIV elements | If a grid is instantiated from a DIV element the API calls to the grid's features do not work as expected. | |
| Virtualization does not work with GroupBy for igGrid | The virtualization feature is not supported with the GroupBy feature for igGrid. |
|
| Virtualization does not work for igHierarchicalGrid | The virtualization feature is not supported for igHierarchicalGrid. |
|
Using both the Infragistics ASP.NET and Ignite UI for jQuery documents assemblies together will cause namespace conflict exceptions.
To resolve this issue, reference either the documents assemblies from Infragistics ASP.NET or the documents assemblies from Ignite UI for jQuery in your application. The documents libraries within these assemblies are the same and can be used to replace one another.
Layout of html elements was modified and rounded corners are rendered around whole editor, but not only buttons.
Application may disable rounded corners by providing custom CSS or overriding default igEditor CSS classes.
Rendering may fail if the base element is TD.
Application should not restrict width of parent element if the base element is TD or it should ensure that actual width of the TD element is not less than the width of the igEditor control. Parent element is not only the parent table but the whole chain of parents up in the DOM hierarchy.
The scenario in which a row template is used and some columns are hidden is not supported.
The solution to this problem is to omit the definitions of the cell of columns you want to hide, from the row template instead of using the igGridHiding control.
If a grid control has some columns explicitly defined and autoGenerateColumns set to true, having columns grouped at initialization will prevent other columns from being grouped at runtime.
The option autoGenerateColumns is true by default so if you are planning to have columns grouped at initialization you have to explicitly define them. It is better to define all of the columns that you want in the grid and set autoGenerateColumns to false.
All grids are generated as igHierarchicalGrid.
You have to explicitly call the AutoGenerateLayouts(false) method of the grid helper with argument false and a flat grid will be generated by the MVC helper for grids.
The scenario where some columns' widths are defined in percentage, while others' are in pixels (or not specified at all) is not supported.
Define all column widths in one unit of measure: percentage or in pixels, but do not mix the two.
When a grid control does not have width defined, its header and footer elements (caption, pager, group-by area etc.) are rendered with a smaller width than the records table in Microsoft Internet Explorer® 7.
The solution to this problem is to define the width for the grid explicitly.
If a grid is instantiated from a DIV element, the API calls to the grid's features did not work as expected.
The calls to the API of the grid's features should rely on the table that they are actually attached to: [gridElementId]_table. If the grid is bound to a DIV with id attribute "grid1" the easiest way to reference that table is to use either the grid's id() or widget() API methods like shown here:
In JavaScript:
$("#" + $("#grid1").igGrid("id")).igGridPaging("option", "pageSize", 2)
or
In JavaScript:
$("#grid1").igGrid("widget").igGridPaging("option", "pageSize", 10)
The virtualization feature is not supported with the GroupBy feature for
igGrid.
The virtualization feature is not supported for igHierarchicalGrid.
View on GitHub