Infragistics

10/13/2026

Most AI coding demos show the finished result and skip the parts that make an integration production-ready.

Today at 11:00 AM ET / 8:00 AM PT, our COO Jason Beres builds an embedded analytics integration live, from a prompt to a working app, using Claude, GitHub Copilot, and Reveal agent skills. Then he shows how Reveal's AI SDK and MCP support put conversational analytics inside the product your users touch.

60 minutes, free, live.

Join the live build:
https://buff.ly/mrjFAvy

10/09/2026

A popup should not stay visible after its control scrolls out of view.

Ignite UI for React 19.9.0 changes that default. Popups for Select, Combo, Dropdown, date pickers, and other controls now hide while their anchor is scrolled out of view. Before, they stayed visible. Set `scrollStrategy="scroll"` if your app needs the previous behavior.

After upgrading, open one of those popups inside a scrolling container, scroll its control out of view, and check that it does what your app expects.

Review the 19.9.0 popup behavior change:
https://buff.ly/Wx2jYp3

19.9.0 - 2026-09-28 Added New components from igniteui-webcomponents 7.3 and 7.4 ( #198, #202): IgrBreadcrumbs and IgrBreadcrumb IgrColorPicker IgrQrCode IgrVirtualScroll Changed Updated publi...

10/07/2026

A guessed import path can stop generated code before it runs.

Ignite UI CLI 15.8.0 added `resolve_import` to its MCP server. It returns the exact import statements for the symbols you ask for, grouped by module, across Angular, React, Web Components, and Blazor.

A coding agent can look up the module path instead of guessing one that ends in "has no exported member" or "cannot find module."

Before your coding agent writes an Ignite UI import, ask it to resolve the component symbol and check the returned module path.

Review the 15.8.0 import lookup:
https://buff.ly/QRL22cc

10/06/2026

AI coding assistants often invent a component API that is not the one in your project.

Ignite UI's Enterprise MCP toolchain gives assistants like GitHub Copilot, Cursor, Claude, and JetBrains AI live Ignite UI docs, scaffolding, and design tokens across Angular, React, Web Components, and Blazor. The assistant works against the library you ship with, not only what it remembered in training.

If your team already uses Ignite UI, that is the gap this closes.

App Developer Magazine on the launch:
https://buff.ly/8wUj81z

The newly released Ignite UI Enterprise MCP toolchain by Infragistics bridges the gap between artificial intelligence coding assistants and production-ready enterprise applications.

10/06/2026

Adding a child row should target the parent your code specifies.

Ignite UI for Angular 22.2.1 changes Tree Grid's beginAddRowByIndex(index, true): the add-row UI now opens for a child of the row at that index, as documented. Before, it used the preceding row, at index - 1.

If your code shifted the index to make up for that offset, call the method for a known parent after upgrading and check that the add-row UI targets that row.

Review the 22.2.1 Tree Grid behavior change:
https://buff.ly/vuWHdJ4

Ignite UI for Angular is a complete library of Angular UI components with the fastest grids and charts, dock manager, and more. - IgniteUI/igniteui-angular

09/30/2026

A Pivot Grid should not wait for another interaction to show a row dimension your code already added.

Ignite UI for Angular 22.1.5 fixes that for insertDimensionAt. The grid now updates as soon as the row dimension is added. Before, after zone.js was removed from the library, the grid could stay unchanged until something else triggered change detection.

If your app adds row dimensions in code, add one and check that the grid updates without another action.

Review the 22.1.5 Pivot Grid fix:
https://github.com/IgniteUI/igniteui-angular/releases/tag/22.1.5

09/29/2026

A visible form label should name the control that receives focus. A click on it should focus that control too.

Ignite UI for Web Components 7.4.1 fixes both for Checkbox, Switch, and Radio. An external label, or one that wraps the control, now names it, and a click focuses and toggles it. Before, the control had no accessible name and the click did nothing. For Combo, its own label or an external one now names the input, instead of the selection status text ("No options selected").

When you test a form, check the focused control's accessible name, not only the label on screen.

Review the 7.4.1 form-label fixes:
https://github.com/IgniteUI/igniteui-webcomponents/blob/7.4.1/CHANGELOG.md #741---2026-09-25

09/28/2026

A virtualized list can render fewer elements and still get item identity wrong.

Ignite UI for Web Components 7.4.1 adds keyFunction to Virtual Scroll. It supplies a key for each item, so that item keeps its element while it remains in the rendered window, even when its position in the data changes. Without it, the index is the key.

Virtual Scroll now also reuses item elements by default. If your item template holds unbound DOM state, such as a checkbox without a checked binding, bind it before you upgrade.

For lists that reorder in place, you can now make identity follow the item rather than its position.

Review the 7.4.1 Virtual Scroll changes:
https://github.com/IgniteUI/igniteui-webcomponents/blob/7.4.1/CHANGELOG.md #741---2026-09-25

Ignite UI for Web Components is a complete library of UI components, giving you the ability to build modern web applications using encapsulation and the concept of reusable components in a dependen...

09/23/2026

A breadcrumb trail is less useful if it shows the path but not the current page.

Ignite UI for Web Components 7.4.0 adds Breadcrumbs (igc-breadcrumbs / igc-breadcrumb). Mark an item as current and it sets aria-current="page"; separators and item content can be customized.

That gives teams a navigation trail they can style for the app while preserving an explicit current-page cue for assistive technology.

See the 7.4.0 changes:
https://github.com/IgniteUI/igniteui-webcomponents/blob/7.4.0/CHANGELOG.md #740---2026-09-23

Ignite UI for Web Components is a complete library of UI components, giving you the ability to build modern web applications using encapsulation and the concept of reusable components in a dependen...

09/22/2026

Choosing the wrong hierarchy model rarely fails on day one. It fails when every level needs different columns and the grid no longer fits the data.

In Ignite UI for React, use Tree Grid when each level repeats the same schema, such as categories or an org chart. Use Hierarchical Grid when each level represents a different entity, such as customer → order → line item.

Start with the data model, not the expand icon. That decision avoids a much larger refactor later.

Compare the two approaches:
https://www.infragistics.com/blogs/react-tree-grid-vs-hierarchical-grid