Infragistics Ignite UI Lanzamientos

• IgxChipComponent
  • Added the outlined property to the component. When set to true, the Chip will have an outlined style.
• Theming
  • Breaking Change - The chip-theme properties - $focus-outline-color and $focus-selected-outline-color were replaced with $focus-shadow-color and $focus-selected-shadow-color.

• Calendar
  • igc-calendar now exports the label-inner, months-row and years-row parts. The pickers export them as calendar-label-inner, months-row and years-row. The views rendered these parts but did not export them, thus you could not style them through the calendar.
• Chip
  • New outlined property. When you set it to true, the chip shows an outlined style.
• Icon
  • registerIcon and registerIconFromText now accept a RegisterIconOptions object as their third argument, in addition to the plain collection string.
  • stripMeta: true removes the <title> and <desc> elements from the stored SVG. This prevents the native browser tooltip on hover.
  • The title text stays available as the aria-label of the host igc-icon element.
  • The component removes the aria-labelledby and aria-describedby references on the root <svg> that point to the removed elements.
• Mask input, Date time input, Date range picker
  • The masked editors now support the standard undo and redo shortcuts: Ctrl + Z / Cmd + Z to undo, and Ctrl + Y, Ctrl + Shift + Z / Cmd + Shift + Z to redo. These shortcuts did nothing before, because each render of the masked text sets the value of the native input and clears the browser undo stack.
  • A sequence of typed characters, or a sequence of deletions, becomes one undo step. A caret movement, a paste, a drop, a cut, a spin of a date part, and an IME composition each start a new step.
  • A restored step emits igcInput, thus composite hosts and two-way bindings follow the undo. In the date editors the restored text stays an uncommitted draft, and the component emits igcChange on blur only if the committed value changed.
  • The history stays through focus changes. The component discards the history when you set the value programmatically, when the form resets the control, or when the mask, prompt or input-format pattern changes.
• QR Code
  • New igc-qr-code component. It renders a scannable QR code as an SVG from the value property, and encodes the data in numeric, alphanumeric or byte mode.
  • Set an explicit version (1-40) and error-level (L/M/Q/H), or let the component select the smallest version and level that hold the data.
  • size and margin control the rendered pixel dimensions and the quiet zone (in modules) around the code.
  • logo-src adds an optional branding logo. logo-size and logo-margin control how much of the scannable area the logo covers. The component increases the error correction level for the logo, unless you set the level.
  • dot-style and square-style set the shape of the data modules and of the finder-pattern corners (square, circle, rounded).
  • The --ig-qr-code-background, --ig-qr-code-dark-color, --ig-qr-code-corner-square-color and --ig-qr-code-corner-dot-color CSS custom properties control the theme. The component exposes the background, dots, corner-square and corner-dot CSS parts.
• Splitter
  • startCollapsed and endCollapsed properties. Use them to read and to set the collapsed state of each pane.
  • igcLayoutChanged event. The component emits it after a user resize or a change of the expansion state. The payload holds the current layout (startSize, endSize, startCollapsed, endCollapsed).
• Tabs
  • selectedTab property. It returns the selected igc-tab element, or null.
  • select() now also matches the label of a tab, in addition to its IDREF. Thus you can pass the value that selected reports back into it.
• Virtual Scroll
  • New igc-virtual-scroll component. It renders large or unbounded lists efficiently, because it renders only the items in the viewport plus a configurable overScan.
  • Supports vertical and horizontal orientation, and RTL layouts.
  • Item sizes can be fixed, estimated with estimatedItemSize, or fully variable. The component measures each rendered item and corrects its estimate automatically.
  • scrollToIndex() scrolls to a given item, with a configurable alignment (block/inline) and scroll behavior (auto/smooth). The component corrects the target offset while it measures the items around it, thus the requested item stops in the correct position.
  • igcDataRequest event. The component emits it when the scroll position comes near the end of the loaded data. Use it for infinite scroll and for remote data.
  • igcStateChange event. The component emits it after each render pass, with a snapshot of the current virtual window (startIndex, endIndex, viewportSize, totalSize).
  • layoutComplete property. This promise resolves when the current render pass, and all subsequent renders that item measurement causes, are complete.
  • The component operates correctly above the maximum scroll coordinate of the browser. Lists that are much larger than the DOM permits continue to scroll and to render correctly.
• Button group
  • Behavioral change: a disabled group no longer sets disabled on its buttons. The buttons inherit the state. Thus a button that is disabled on its own stays disabled when you enable the group again, and the buttons that you add to a disabled group are also disabled.
  • Improved accessibility: the single and single-required modes expose a radiogroup with radio buttons, instead of toggle buttons with aria-pressed. The focused CSS part of igc-toggle-button is now documented.
• Carousel
  • The component now delegates focus to its indicator container, its navigation buttons, or the first focusable element in the active slide, in this sequence.
• Chip
  • The focus-outline-color and focus-selected-outline-color CSS variables are replaced by focus-shadow-color and focus-selected-shadow-color.
• Combo
  • The dropdown list now uses the new igc-virtual-scroll component instead of the third-party @lit-labs/virtualizer package.
• Date time input, Date picker, Date range picker
  • Behavioral change: the components no longer change the value property while the user types. value now holds only a committed value and changes together with the igcChange event, which the components still emit on blur. Before, value changed on each keystroke - it became null for an incomplete mask, and the parsed date when the mask was full - and no event announced the change.
  • Thus you can use the components in templates that bind value externally, such as an edit template in igc-grid. Before, each re-render during typing applied the stale bound value again and reset the editor, thus you could not enter a new date.
  • The value that the user types - and the result of a spin of a date part or of Ctrl + ; - is available in the detail of the igcInput event. The payload of the event does not change.
  • A spin of a date part in a focused editor also defers to the commit on blur. A programmatic stepUp() or stepDown() on an unfocused component changes value immediately, as do clear(), setRangeText() and direct assignments.
  • In igc-date-picker and igc-date-range-picker the calendar continues to follow the typed date during editing, as before.
• Dropdown
  • Behavioral change: the component no longer emits igcChange when you select the item that is already selected. The list still closes, as before.
  • Improved accessibility: the target element declares aria-haspopup="listbox" instead of aria-haspopup="true". While the list is open, the target holds aria-activedescendant that points at the item that keyboard navigation is on, thus screen readers announce the highlight. The component sets an id only on items that have none. It also removes all the attributes that it wrote on the target when it no longer uses that target.
• Library
  • Updated the optional peer dependencies for dompurify, marked and shiki to their latest stable versions.
  • Removed the @lit-labs/virtualizer dependency. The new igc-virtual-scroll component now supplies the virtualization.
• Tabs
  • Behavioral change: the scroll buttons now scroll to the nearest tab that is not fully visible, instead of a fixed step of 180px. A tab below a scroll button counts as not visible. Thus one click brings exactly one tab into view and does not overshoot it.
  • Improved accessibility: the tab headers expose aria-posinset and aria-setsize, the strip declares its aria-orientation, and the selected panel is focusable. Thus keyboard users can reach panel content that holds no focusable elements of its own. The strip also keeps a tab stop when no tab is selected.
  • The component now finds igc-tab elements that come through an intermediate slot. Thus another component can wrap igc-tabs.
• Tooltip
  • Behavioral change: a tooltip that closes from a hide trigger now waits exactly hide-delay. Before, it waited through an additional, undocumented stage of 180ms, thus the real delay was hide-delay + 180ms.
  • Behavioral change: in sticky mode the default close button hides the tooltip immediately and does not wait for hide-delay. Before, an explicit close took almost half a second.
  • Behavioral change: focusin and focusout are now part of the default show-triggers and hide-triggers. Thus a tooltip opens when its anchor gets keyboard focus, and closes when the focus leaves the anchor.
  • Improved accessibility: the anchor points at the tooltip with aria-describedby, thus screen readers announce the content as the description of the anchor. The tooltip generates an id only when it has none, keeps the references that are already on the anchor, and removes its own reference when it no longer describes the anchor.
  • Improved accessibility: in sticky mode the default close action is a labeled <button> and not a bare icon. Thus you can reach and operate it from the keyboard. The new close-button CSS part exposes it.

• Button group
  • Single selection compared the values of the buttons. Thus buttons without a value, or with the same value, could not take the selection: a click on a second button only cleared the first. The component now tracks the selection per element.
  • selectedItems added to the current selection instead of a replacement of it, and ignored buttons whose value is an empty string.
  • You could still interact with a disabled group through buttons that you added after the group became disabled.
  • focus(), blur() and click() on igc-toggle-button threw an error when you called them before the first render.
  • Toggle buttons that are not direct children of the group changed its selection state. This could keep two buttons selected in a single selection mode, or remove the selection.
• Calendar
  • A calendar with more than one visible month announced each navigation one time per month, because the off-screen live region with the current period was part of the navigation of each month. There is now one live region for the full calendar.
  • A calendar with more than one visible month exposed one tab stop per month. Thus the tab key moved into the grid of each month instead of out of the calendar. Only the active days view now holds the tab stop of its active date.
  • The component now resolves time-only date strings against the current local date and not the UTC date. Before, the parsed date moved by one day near midnight in some time zones.
  • week-start stayed stale until a subsequent update corrected the view. The component now resolves and renders week-start correctly on the initial render.
  • Keyboard navigation over a large number of disabled dates could hang the browser. The navigation is now a no-op in this condition.
• Carousel
  • A pointer over a carousel, or focus inside it, started the rotation of a carousel that you paused through pause(). The component now starts the rotation again only if an interaction paused it.
  • A change of interval set the playing state and left the paused state as it was, thus isPlaying and isPaused were both true. A clear of interval also reported the carousel as playing, without a rotation. Both states now describe the rotation correctly.
  • An interaction that changes nothing - a key press at the last slide with disableLoop - left a timer that ran without a rotation, and nothing cleared it.
  • A key press at the last slide with disableLoop moved the focus to an indicator on the next slide change that came from select(), next() or prev().
  • A carousel with fewer projected igc-carousel-indicator elements than slides threw a TypeError during render. The indicators now map to the slides by position, for any count of each.
  • The removal of the active slide left the carousel with no active slide. The slide that takes its position now becomes active.
  • The component set aria-controls on the host, where it described nothing. Each projected indicator now carries it, and points at the slide that it selects.
  • Slides that entered an empty carousel after its first render stayed inactive, thus the carousel showed nothing. The authored active slide, or the first slide, now becomes active.
  • A change of interval on a carousel that left the DOM started a timer that no rotation used. Only a return to the DOM now starts the timer again.
  • A carousel that left the DOM before its first render completed threw an unhandled TypeError from the gestures controller. The controller now verifies that the element is still present.
  • The documentation of the component now includes the indicator slot.
• Chat
  • With adoptRootStyles enabled the component ignored the stylesheets that entered the document after the initial adoption. Thus custom renderers whose styles are injected during view creation - Angular component styles, for example - showed unstyled content. The component now tracks the document stylesheets while the option is on, and applies each addition or removal to the shadow roots that adopted them, including stylesheet links that load later.
  • Adoption of the document styles no longer removes the theme styles of the message and the input parts. Before, the adoption built the stylesheet list from the static styles of the component only.
• Dropdown
  • Enter on an open dropdown before any arrow key threw a TypeError instead of doing nothing. The type of the item that keyboard navigation moves from declared that the item is always present, but the item is unset until you navigate the list or select something.
  • Keyboard navigation stopped on a dropdown that opened at an explicit target, after a close and a subsequent open without that target, because the close removed the target together with its key event listeners. The component now keeps the target until another target replaces it.
  • A dropdown that opened at an explicit target and then opened again through its own target slot stayed at the previous, detached element. The component now always resolves the current anchor and gives it to the popover.
  • A call of show() with another target while the dropdown is open left aria-expanded on the previous element and leaked its key event listeners.
  • show() with an id that matches no element threw a TypeError. An unresolved target now keeps the current target. When there is no anchor at all, show() returns false and does not open, because the popover cannot position a list without an anchor and the component would report itself open with nothing on screen.
  • clearSelection() cleared the selection but kept keyboard navigation on the cleared item. Thus the next ArrowDown returned to that item instead of the top of the list.
  • selectedItem continued to return an item that was removed from the DOM. The component now tracks the items that enter and leave the light DOM. It drops the selection when its item goes away, and navigation returns to the current selection.
  • aria-haspopup and aria-expanded stayed on the target element after the removal of the dropdown from the DOM, or after another target replaced it.
  • igc-dropdown-header had no role. Thus it stayed in the accessibility tree as a bare child of the listbox, which can own only option and group nodes. The component now removes it from the tree, as it already did for igc-select-header.
  • The label of an igc-dropdown-group named nothing, because the component renders it in the shadow root of the group, out of reach of the host ARIA. Thus screen readers announced the groups without their label.
• Form associated components
  • Validation messages no longer disappear immediately after the first failed form submission. The invalid state from the submission held only for the update that the submission scheduled. Thus a subsequent re-render - a slotchange from the validation slots, for example - removed the messages, but the invalid styles stayed.
  • The invalid styles now follow the validity state. A control that becomes valid again - a cleared required, a wider min/max, a disabled control - now drops the styles from an earlier interaction or submission.
• Highlight
  • Recent Firefox versions did not paint the matches. ::highlight() rules are tree-scoped: they style only the text nodes in the same tree scope as the stylesheet. The component adopted the rules into its own shadow root, but the text that it highlights is slotted content in the tree scope of the host. Earlier Firefox versions applied such rules across scopes, as Chromium still does. The root node of the host now adopts the stylesheet, and the component adopts it again if it moves to another tree scope.
  • The same fix lets a component inside another shadow root resolve its --background and --foreground custom properties correctly in Chromium. Before, it used the theme defaults.
• Icon
  • An icon that renders through a reference stayed blank when you registered the target icon later, because the component reacted only to registrations that match its own name and collection and not to the resolved target. It now resolves again on each change of the registry.
  • igc-icon declares role="img" only when it has an accessible name: the <title> of the icon, or an aria-label or aria-labelledby on the host. Before, a decorative icon appeared in the accessibility tree as an image without a name.
• Rating
  • Keyboard input, stepUp() and stepDown() produced values such as 0.30000000000000004 with a fractional step. The value, the igcChange payload and aria-valuenow now hold the exact value. stepUp(n) and stepDown(n) also move by n steps, and not to the next step above the result.
  • aria-valuetext reported a value rounded up to the next step, thus it disagreed with aria-valuenow for a fractional value such as 2.5 with step of 1.
  • A non-numeric max or step attribute produced NaN: the component rendered no symbols and announced NaN of 5. Both now fall back to a valid number.
  • The slider had no accessible name without a label. The component now forwards the aria-label of the host, and sets aria-labelledby only when it renders a label.
  • The component now exposes its readonly and disabled state through aria-readonly and aria-disabled.
  • A change of the aria-label of the host after the first render left the accessible name of the slider as it was.
  • igcHover did not fire when the pointer left the component, and then entered again over the same symbol.
• Select
  • ArrowUp on a closed select that had a selection cleared the selection and showed the placeholder, instead of a move to the previous item. The component set the item that keyboard navigation moves from only through its own selection path. Thus a selection through the value property, or through a selected attribute on an item, left that item unset, and a backward step from "no item" went off the start of the list. Navigation now always starts from the current selection. If there is no item to move to, the selection does not change.
  • Type-ahead threw a TypeError on the first character that you type, on a select that had a selection.
  • Type-ahead no longer swallows keyboard shortcuts. The component used a printable key with Ctrl, Cmd or Alt as a search character and prevented its default. Thus Ctrl + C and similar shortcuts did not reach the browser.
  • Selection of the item that is already selected from the open list - by click, Enter or type-ahead - kept the list open. The list now closes and the focus returns, as for any other selection. The component still emits no igcChange, because the selection does not change.
  • The component no longer discards a value that you set before the matching item exists. Frameworks frequently render items asynchronously, and a value that matched nothing at the first render became undefined. The component now keeps the value and resolves it when you add the item, also into an existing igc-select-group. Removal of the selected item also drops the selection, but keeps the value.
  • clearSelection(), and a value that matches no item, kept an internal reference to the item that was selected before, from which the next keyboard navigation then moved.
  • The text in the input now comes only from the main content of the selected item. Before, it also held the content of the prefix and suffix slots of the item, and the comment markers that the templating engine left among its children.
  • navigateTo() no longer tries to focus and to scroll the list while the list is closed and inert.
• Tabs
  • See-through scroll buttons in the Indigo theme. The buttons are sticky and the tab headers scroll below them, but the theme keeps the buttons and the tabs strip transparent, thus the scrolled headers were visible through the buttons. The buttons now paint an opaque surface backdrop below their themed background.
  • The component did not emit igcChange when activation is manual and you activate a tab with Enter or Space. Thus the selection changed without an event.
  • The selection now stays in agreement with the DOM in conditions that made the component inconsistent:
    • selected set to false on the active tab hid its panel, but the tab stayed active internally. Thus you could not select it again.
    • Removal of the last tab left a dangling reference that selected continued to report.
    • select(), the selected attribute and the initial selection could each activate a disabled tab, which a click always refused. A tab with selected and disabled showed its panel together with the selected panel.
    • A disabled active tab kept its panel visible below a greyed-out header. The selection now moves to the first enabled tab, or clears if all tabs are disabled.
  • The start scroll button stayed enabled at the start of the strip under browser zoom or a non-integer device pixel ratio, where the scroll offset is fractional.
  • A click on a partially visible tab header scrolled the strip two times.
  • Less rendering work: a scroll of the strip no longer schedules an update per scroll event, and a change of the selection no longer causes an unnecessary layout pass.
• Tooltip
  • show() and hide() did not cancel a queued transition in the opposite direction. Thus a tooltip could open immediately after a call to hide it, and close immediately after a call to show it.
  • A pointer that moved back over the anchor during the hide animation closed the tooltip and kept it closed, although the pointer never left the anchor.
  • Interaction with the original anchor, while a tooltip from show(target) was open, desynchronized the component: it reported open === false while it stayed on screen, and you could no longer close it.
  • with-arrow set at runtime did not give the arrow element to the popover. Thus the arrow had no position and no styles until an unrelated re-render corrected it.
  • Delayed show and hide transitions returned a promise that never settled.
  • A close with Escape emitted igcClosed even when there was nothing to close.
• Tree
  • Large or deeply nested trees are much faster:
    • A read of path on a tree item, and each operation built on it such as the activation of a nested item, cost 2^depth and not depth, because the component walked the ancestor chain two times per level. One read at depth 20 took ~23ms; it now takes less than a microsecond at any depth.
    • Keyboard navigation is approximately 5 times faster (~1.24ms to ~0.24ms per keypress on a tree with 1554 items). A lazy walk that prunes the collapsed branches now supplies the navigable set. Before, the component materialized all items and filtered them through the ancestors of each item.
    • Removal of a subtree while items are selected is approximately 2 times faster (~134ms to ~71ms for 259 items in cascade mode). Before, each removed item ran the full cascade reconciliation again, although the topmost removed item covers its full subtree.
    • tree.items, select() over a full cascade tree, and the expansion or the collapse of all items are each 25-45% faster.

• IgniteUI.Blazor
  • Added axis visibility properties to Axis and all XYChart-derived charts, allowing individual axis elements to be toggled without style overrides:
    • AreLabelsVisible - Hides the tick label text while the label panel keeps its layout slot.
    • AreTickMarksVisible - Hides the tick mark strokes.
    • AreAnnotationsVisible - Hides axis annotations (e.g. FinalValueLayer badges).
    • IsLabelPanelVisible - Collapses the entire label panel to zero extent.
    • The corresponding chart-level forwarding properties XAxisAreLabelsVisible, XAxisAreTickMarksVisible, XAxisAreAnnotationsVisible, XAxisIsLabelPanelVisible, YAxisAreLabelsVisible, YAxisAreTickMarksVisible, YAxisAreAnnotationsVisible and YAxisIsLabelPanelVisible were added on IgbCategoryChart, IgbFinancialChart and other XYChart-derived charts.
  • Added LegendItemBadgeMarkerSizeScaling to series, which controls how legend badges scale with the series MarkerSize. Supported values are Auto (default, interpolates the badge between 1x and 2x), None (badge keeps its default size) and Linear (badge scales directly with MarkerSize). The resolved sizes are exposed through the read-only ActualLegendItemBadgeMarkerWidth and ActualLegendItemBadgeMarkerHeight properties.
  • Added StartInset and EndInset to IgbLinearGraphRange (used by IgbLinearGauge and IgbBulletGraph) and to IgbRadialGaugeRange. The properties trim a range's start and end edges inward by a distance measured in device-independent pixels, producing a consistent gap between adjacent ranges regardless of the gauge's size or value range. Both default to 0, so ranges continue to meet flush unless an inset is set.
• IgniteUI.Blazor (Grids)
  • Updated the internal Ignite UI for Angular reference from 21.2 to 22.0, refreshing the generated models for IgbGrid, IgbTreeGrid, IgbHierarchicalGrid and IgbRowIsland, including the new GridBase, HierarchicalGridBase and RowIslandBase shared surfaces.

• IgbInput and other web inputs - Components were not registered on load; defineAllComponents registration was restored.
• IgbGrid - Filtering event detail payload now uses FilteringExpressionsTree instead of the previous incorrect type.
• Web inputs - ReportValidity and CheckValidity returned the wrong type on IgbCheckbox, IgbCombo, IgbDatePicker, IgbDateRangePicker, IgbInput, IgbRating, IgbSelect, IgbSlider and IgbTextarea.
• Web inputs - Focus options were not marshalled correctly; they are now treated as a plain object.
• IgbChat and other web components - Enum-typed properties were not serialized correctly when passed through the renderer element.
• IgbRadialGauge, IgbLinearGauge, IgbBulletGraph - Null reference exception could occur in the gauges.
• IgbSpreadsheet - Horizontal lines were not displayed correctly, and SVG shapes shifted position as line thickness changed.
• IgbDataPieChart - SeriesPointerEnter did not reach handlers on hover, and aggregated-away buckets were incorrectly measured in the angular range.
• IgbDataPieChart - Slice layers showed the wrong image when a requested image changed before a prior image finished loading.
• IgbDataChart - Chart was not disposed correctly on destroy.

• New Features
  • Theming
    • Component structural styles are now scoped and tree-shakable - they ship inside each component's own bundle instead of a single global, all-or-nothing theme stylesheet. An app now pays for CSS only for the components it actually imports.
    • Design tokens for all four design systems (Material, Bootstrap, Fluent, Indigo) × light/dark are emitted once per theme into the global preset (e.g. igniteui-angular.css). As a result of those changes, the pre-built theme files are roughly half the size (~49% smaller raw, ~58% smaller gzip).
    • Finalized the migration to the tokens() mixin as the single way to apply a component theme, replacing the individual per-component wrapper mixins (avatar(), dialog(), checkbox(), tabs(), etc.) across the rest of the library, following the same pattern already introduced for the Grid family in 22.0.0.
    • The 22.1.0 ng update migration performs a syntactic replacement of removed wrapper mixins, but cannot reliably infer whether an application's customization was intended as a universal override or as a local theme. Review migrated tokens() calls and add $mode: 'scoped' where one of the cases above applies.
    • Cascade layering (ig.reset → ig.base → ig.material/ig.bootstrap/ig.fluent/ig.indigo → ig.derived) keeps precedence deterministic between structural styles, design-system overrides, and derived/contextual tokens now that styles are split across component bundles and the global preset.
  • Breaking Changes
    • The individual per-component Sass theme wrapper mixins (avatar, badge, banner, bottom-nav, button-group, calendar, card, carousel, checkbox, chip, column-actions, combo, date-picker, date-range-picker, dialog, divider, drop-down, expansion-panel, excel-filtering, grid-summary, grid-toolbar, icon, file-input, input-group, list, navbar, navdrawer, paginator, progress-circular, progress-linear, query-builder, radio, select, slider, snackbar, splitter, stepper, switch, tabs, time-picker, toast, tree, and the grid/pivot mixins), which have been marked as deprecated in favor of the generic tokens/css-vars mixins for several major versions, have now been removed. Use the tokens() mixin instead. The ng update migration for 22.1.0 automatically rewrites existing @include <component>(<component>-theme(...)) calls to @include tokens(<component>-theme(...)). This is a syntactic migration; review each replacement and use $mode: 'scoped' for component-local themes as described in the Theming section above.
    • Removed the per-component -typography mixins (badge-typography, dialog-typography, checkbox-typography, etc.). Typography is now applied automatically as part of each component's tokens, so these standalone calls are no longer needed. The ng update migration deletes existing calls (including multi-line and aliased calls) automatically.
    • Removed the deep Sass imports of per-component structural partials (e.g. igniteui-angular/lib/core/styles/components/avatar/avatar-component) and their component() mixin calls. Structural styles are no longer optionally-included Sass — they now ship automatically with each component's bundle. The ng update migration removes these @use statements and matching component() calls automatically.
    • IgxDividerDirective has been replaced by IgxDividerComponent (divider is now a standalone component with its own scoped stylesheet). The ng update migration updates existing imports/usages automatically; IgxDividerModule is unaffected.
    • Some exports moved to a different entry point. An optional (recommended) ng update migration rewrites the affected imports automatically:
      • igniteui-angular/grids/core → igniteui-angular/core: IgxSummaryOperand, IgxNumberSummaryOperand, IgxDateSummaryOperand, IgxTimeSummaryOperand, GridSelectionRange, ISelectionNode, IMultiRowLayoutNode, ISelectionKeyboardState, ISelectionPointerState, IColumnSelectionState, SelectionState, IgxGridTransaction.
      • igniteui-angular/grids/grid → igniteui-angular/grids/core: IGroupingDoneEventArgs.
    • IgSizeDirective ([igSize]) is no longer part of the public API and is no longer exported from igniteui-angular/directives. Set the size directly on the element instead, e.g. style="--ig-size: var(--ig-size-small)", or via a component stylesheet.
• General
  • Strict TypeScript - The library is now built with strict: true (including strictNullChecks) and strictTemplates. The shipped typings are therefore more accurate: members that can be absent are now typed as nullable or optional, and a number of any types were replaced with real ones (for example ColumnType.summaries is now IgxSummaryOperand and ColumnType.calcWidth is string | number | null). Applications compiled in strict mode may need null checks or non-null assertions where the previous, looser typings allowed the code to pass. Runtime behavior is unchanged.
  • IgxGrid, IgxTreeGrid, IgxHierarchicalGrid, IgxPivotGrid, IgxColumnComponent
    • The rowStyles, headerStyles and headerGroupStyles inputs are now typed GridStyleCSSProperty | null instead of any. The new GridStyleCSSProperty interface is exported from igniteui-angular/core.
  • Removed Hammer.js dependency
    • The hammerjs and @types/hammerjs peer dependencies have been removed. All touch gesture support (Carousel swipe, Navigation Drawer pan/swipe, List Item pan, Time Picker vertical scroll, Grid Cell double-tap on iOS) is now implemented with native Pointer Events / Touch Events APIs.
    • HammerGesturesManager and related types (HammerInput, HammerStatic, HammerManager, HammerOptions) are no longer exported from igniteui-angular/core.
    • The ng add schematic no longer prompts for, or installs, hammerjs.
    • If your application imported hammerjs solely for Ignite UI components, you can safely remove it from your package.json dependencies, angular.json scripts/polyfills, and any import 'hammerjs' statements.
  • igxList
    • igx-list-item no longer tracks touch gestures when neither allowLeftPanning nor allowRightPanning is enabled, so pressing an item no longer captures the pointer or suppresses the touch scrolling of the list. When panning is enabled, the gestures are processed outside of the Angular zone, which keeps continuous touch dragging of large (virtualized) lists smooth.

• Angular 22 compatibility - All Ignite UI for Angular components are now fully compatible with Angular 22.
• Standalone component support - Components can now be used directly in standalone Angular applications without NgModule. New provide() functions (e.g. provideIgxCategoryChart()) let you register component feature sets through bootstrapApplication() providers, and imperative register() functions are available for DI-free setups.
• Per-component entry points for improved tree-shaking - Each package now exposes named subpath entry points (e.g. import 'igniteui-angular-charts/category-chart') that register only the feature set you need. The root package import remains fully side-effect-free and tree-shakeable, so you only pay for the components you use. For DataChart, graduated entry points such as data-chart-category, data-chart-scatter, and data-chart-financial let you pull in individual series families without bundling the entire chart.

• DataChart - An error is thrown when destroying chart with a data tooltip layer.

• Form associated custom elements with external labels
  • External <label> associations are now resolved to the underlying native input of form-associated controls. Associating a label with IgcInput, IgcMaskInput, IgcTextarea, IgcDateTimeInput, IgcSelect, IgcCombo, IgcDatePicker, or IgcDateRangePicker - either through the for/id IDREF mechanism or by nesting the component inside the <label> - now correctly exposes the label to assistive technologies and focuses the inner input on label activation.
• AI-Assisted Development
  • Improved grid related skills.

• Tabs
• Prevent selected tab header from scrolling into view on initial render.

• IgbChat (Preview) - a chat component with messages, reactions, suggestions, and typing indicators.
• IgbSplitter - resizable two-pane layouts with collapse, keyboard support, and nesting.
• IgbHighlight - search and highlight text projected into the component.
• IgbDockManager - two-way Layout binding plus new pane and tab events (Dock Manager 2.1).
• Four Agent Skills - components, grids, theming, and design-to-view guidance for AI assistants.

• Popover based components
  • Popover reposition jitter in position: sticky ancestors.
• Tile Manager
  • Text selection in Safari during drag operation.
  • Tile manager height collapse when a spanning tile is maximized.

• Theming
  • Added derived themes for the Grid and related internal components. When a parent component theme is included, its internal controls now derive their tokens from the parent theme colors, keeping nested buttons, icons, inputs, dropdowns, checkboxes, scrollbars, chips, and other helper components visually aligned. The derived themes are introduces for the following components:
    • Grid
    • Excel Filtering
    • Grid Toolbar
    • Paginator
    • Column Actions
    • Query Builder and Advanced Filtering Dialog
    • The derived themes are applied through the existing component theme mixins, so no additional mixin call is required. To style the whole IgxGrid, provide the $background, $foreground, and $accent-color properties to grid-theme() and include the generated theme with tokens(). The $foreground property is optional; when omitted, it is derived automatically as a contrast color for the background. Internal components inherit derived tokens from the parent component theme.
  • Breaking Changes
    • IgxInputGroupComponent, IgxSelectComponent, IgxDatePickerComponent, IgxDateRangePickerComponent, IgxTimePickerComponent
    • The default type has changed from line to box. The ng update migration automatically adds type="line" to existing instances that do not already have an explicit type binding to preserve their appearance.
  • Behavioral Changes
    • IgxCarouselComponent
      • Changed the default tab order of the component; focus now flows starting with the active slide indicator, navigation buttons, or the first focusable element in the active slide, whichever is available.
  • General
    • Touch Gestures (HammerJS) (optional)
      • HammerModule, previously exported from @angular/platform-browser, is no longer available in Angular 22. Touch gesture support (Slider, Drag & Drop, Carousel swipe, Navigation Drawer) is optional.
    • IgxSelectComponent
      • The default positioning strategy has changed from the internal overlap strategy to AutoPositionStrategy. The dropdown now opens below (or above, if there is not enough space) the input element, consistent with other connected components.
    • Added IgxSelectOverlapPositionStrategy - a new publicly exported strategy that preserves the previous behavior of aligning the selected item's text over the input text.

• AI-Assisted Development
  • Decreased token consumption of skills and improved migration skill from grid lite to premium offering.
• Snackbar, Toast
  • Abstracted container positioning property into a new type NotificationPositioning.

• Expansion Panel
• Line height for title and sub-title slots.

• LLM Agent Skills (updated) - four in-package skills teach AI agents React component usage, theming, design-to-code, and bundle optimization.
• CLI MCP Server: React support - ig mcp serves React component docs, full API reference, and scaffolding guidance to any connected AI assistant.
• Invoker Commands API - declarative --show, --hide, --toggle via command and commandFor props, no JavaScript wiring required.
• Platform Popover Upgrades - Nav Drawer moves to native Popover API; Snackbar and Toast gain top-layer positioning property.
• Date Range Picker inline editing - edit range value directly via a single input field.
• Nav Drawer overlay CSS part removed - target base::backdrop or --ig-overlay-background-color instead.
• Form controls: Enter key submits the associated form - IgrInput, IgrMaskInput, IgrDateTimeInput, IgrCheckbox, IgrRadio, IgrSwitch, IgrDatePicker, and IgrDateRangePicker now match native HTML form element behavior on Enter. No code changes required; review any custom Enter-key handlers that manually call form.submit() to avoid duplicate submissions.
• Input: date/time type theming - date, time, datetime-local, week, and month input types now receive full theming support and consistent floating label behavior across all supported themes.
• Localization: resource strings deprecated - the per-component resourceStrings interfaces for Calendar, Chat, Date Picker, and Date Range Picker are deprecated. Components now use igniteui-i18n resource keys. Provide a complete resource strings object rather than setting individual string properties.

• Button Group selected state border color mismatch in focused and hover states; Combo display value not restored when tabbing out in single-select mode with partial search text; Stepper step components now correctly receive context when connected to the DOM before their parent stepper.

• Resolved CSP violations coming from the usage of inline styles in disposable element created for measurements.

• Date Range Picker
  • Added support for editing the date range value directly via a single input field.
• Nav Drawer
  • The drawer for non-relative positions are now implemented using the native Popover API, providing built-in modal semantics, focus trapping, and accessibility support.
  • Added keepOpenOnEscape property - prevents the drawer from closing when the user presses the Escape key (non-relative positions only).
  • Added igcClosing event - emitted just before the drawer is closed by user interaction. Cancelable.
  • Added igcClosed event - emitted just after the drawer is closed by user interaction.
  • The overlay CSS part has been removed. Users of the component can target the base part's ::backdrop pseudo-element, the --ig-overlay-background-color variable or use the theming package.
• Invoker Commands API
  • igc-button and igc-icon-button now support 'command' and 'commandfor' properties, enabling declarative control of target components without JavaScript.
  • igc-banner, igc-dialog, igc-nav-drawer, igc-snackbar, and igc-toast now respond to --show, --hide, and --toggle commands dispatched by an invoker button.
• Snackbar
  • Added positioning property (viewport | container). The component now renders as a popover in the browser top layer. Setting positioning to container anchors the component to its nearest visible ancestor instead of the viewport.
• Toast
  • Added positioning property (viewport | container). The component now renders as a popover in the browser top layer. Setting positioning to container anchors the component to its nearest visible ancestor instead of the viewport.
• AI-Assisted Development
  • Updated and enhanced the library provided skills.
• Form controls
  • IgcInput, IgcMaskInput, IgcDateTimeInput, IgcCheckbox, IgcRadio, IgcSwitch, IgcDatePicker, and IgcDateRangePicker now submit their associated form on Enter key press, matching native browser behavior.
• Input
  • Added theming support for date, time, datetime-local, week, and month input types, ensuring consistent styles and floating label behavior across all supported themes.
• Deprecated
  • Localization
    • The old resource string interfaces for Calendar, Chat, Date Picker, and Date Range Picker are deprecated. Components now use the new igniteui-i18n resource keys. Setting individual resourceStrings properties directly is no longer supported; provide a complete resource strings object instead.

• Internal library metadata issue.
• Button Group
  • Selected state border color mismatch in focused and hover states.
• Combo
  • Display value not restored correctly when tabbing out in single-select mode with a partial search text.
• Stepper
  • Step components connected to the DOM before their parent stepper now correctly receive context after being adopted by a stepper.

• AI-Assisted Development
  • Updated and enhanced the library provided skills.

• Stepper
  • In horizontal orientation, the content area height can now be driven by the active step's content instead of always being sized to the tallest step. A new --body-grid-rows CSS custom property controls the internal row sizing of each step body - its default value of 1fr expands the body to fit its content, while setting it to 0fr collapses the body to zero height, enabling fully variable step heights.

• AI-Assisted Development
  • Updated and enhanced the library provided skills.
• Button group
  • Themes color alignment.
• Circular Progressbar
  • Unified track color CSS variable between progress bars.
• Chip
  • Wrap content inside a new part container and update styles.

• Dropdown
  • Selected item styles problem.
• Linear Progressbar
  • Unified display size across platforms.
• Tree
  • Background style discrepancies.

AI-Assisted Development - Agent Skills

• Added structured knowledge files that teach AI coding assistants (GitHub Copilot, Cursor, Windsurf, Claude, JetBrains AI, etc.) how to work with Ignite UI for React. The skill files are included in the igniteui-react package and also live in the skills/ directory:
  • Components - Identify the right React components for a UI pattern, then install, import, and use them - JSX patterns, events, refs, forms, etc.
  • Customize-theme - Customize styling using CSS custom properties, Sass, and the theming system in React, including using Ignite UI Theming MCP server.
  • Optimize-bundle-size - Reduce bundle size with granular imports, tree-shaking, and lazy loading.
• These skills are automatically discovered when placed in the agent's skills path (e.g. .agents/skills or .claude/skills).

Changed

• IgrDockManager: Updated to use the latest igniteui-dockmanager 2.1.0 with new minResizeWidth and minResizeHeight properties, paneFlyoutToggle event and additional layoutChange event detail.
• Updated to use the latest igniteui-webcomponents 7.1.0 including new Splitter and Highlight container components and fixes.

• Tabs
  • Changing the check state for 'IgbSwitch' inside the tab causes the tab content to disappear.
• Grids
  • Latest version of Blazor Grids shows trial watermark for licensed version.

• Checkbox
  • Updated disabled and indeterminate styles.

• IgrDataPieChart
  • Missing styling properties for the Others Slice.
• IgrDataTooltipLayer
  • TitleTextColor is overriden when chart's TitleTextColor is used.
• Excel
  • Object's Formulas are not round-tripped - Added Excel support for round tripping the camera tool.
  • Saving a VBA Signed Excel file does not keep a signature/certificate.
• IgrDataChart
  • AssigningCategoryStyle args.GetItems is null or not working to update items in the fragment series.

• IgbQueryBuilder
  • Added new component - IgbQueryBuilder - a UI component that allows users to build complex filtering conditions through an intuitive visual interface.
• IgbGrid, IgbTreeGrid, IgbHierarchicalGrid, IgbPivotGrid
  • Improved performance by dynamically adjusting the scroll throttle based on the data displayed in grid.
• IgbGrid, IgbTreeGrid, IgbHierarchicalGrid
  • Added PDF export functionality to grid components. Grids can now be exported to PDF format alongside the existing Excel and CSV export options.
• IgbThemeProvider
  • Added new component - IgbThemeProvider - allows scoping themes to specific page sections using Lit's context API, enabling multiple themes on a single page. Works in both Shadow and Light DOM.
• Badge
  • New dot type, improved outline implementation following WCAG AA accessibility standards and theme based sizing.
• Checkbox
  • New tick-width CSS property.
• Combo
  • New disableClear property which disables the clear button of the combo component.
• Mask input
  • Transform Unicode digit code points to ASCII numbers for numeric patterns.
• Enhancements
  • Accessibility color adjustments for Button, Button group, Calendar, Checkbox, Date picker, date range picker, Nav drawer, Radio group, Stepper.
  • Updated and aligned styles with the design kit for Button, Calendar, Carousel, Combo, Date picker, Date range picker, input, Select, Textarea.
  • Improved keyboard navigation experience and grouping (now using native Math.groupBy) for Combo.

• IgbDataChart
  • DataChart skips rendering axis when there are no labels.
  • AssigningCategoryStyle args.GetItems is null or not working to update items in the fragment series.
  • Exception editing a doughnut chart - DivideByZeroException.
• IgbGrid
  • Improve IgbGrid BodyTemplate Performance (C#/.NET templating).
• IgbDataPieChart
  • Added OthersCategory styling properties to DataPieChart.
• IgbDateTimeInput
  • IgbDateTimeInput Prompt parameter is not propagated to the underlying Web Component prompt property.
• IgbMaskInput
  • IgbMaskInput Prompt parameter is not propagated to the underlying Web Component prompt property.
• IgbPivotGrid
  • IgbPivotGrid exposes SnackbarDisplayTime, but the property is not applicable and causes false test failures.
• IgbDataTooltipLayer
  • TitleTextColor is overridden when chart's TitleTextColor is used.
• Excel
  • Fixed Excel Formula parser - Workbook.Load() throwing a Excel.FormulaParseException.
  • Object's Formulas are not round-tripped - Added Excel support for round tripping the camera tool.
  • Saving a VBA Signed Excel file does not keep a signature/certificate.
• Calendar
  • aria-hidden state for weeks outside of the current month.
  • Focus styles for month/year views.
• Date Picker
  • CSS border for slotted actions in dialog mode.
• Input
  • Placeholder color on focus.
  • CSS border when suffix slot content is present.
• Textarea
  • Align bottom padding to the design system.
• Validation
  • Slotted validation text follows the current theme.
• Tile Manager
  • Header is hidden only when there is no content and maximize/fullscreen are disabled.
• Theming
  • Resolve initial theme based on document computed styles rather than stylesheets.
• Sass Theme Support
  • Checkbox - styled using Sass tools from the theming package.
  • Chip - styled using Sass tools from the theming package.
  • Combo - styled using Sass tools from the theming package.
  • Select - styled using Sass tools from the theming package.
  • Snackbar - styled using Sass tools from the theming package.
  • Added missing shadows to components.
  • Tabs - fixed non-working Sass theme parameters.
  • Textarea - updated Sass themes.
  • Radio - styled using Sass tools from the theming package.
  • Switch - styled using Sass tools from the theming package.
  • List - styled using Sass tools from the theming package.
• Combo
  • Notch border styles.
• Checkbox and Switch
  • Internal ripple opacity when hovering over slotted content in the helper-text slot.
• Dialog
  • Underlying dialog element now has display: contents and won't participate in DOM layout.
  • keepOpenOnEscape not preventing the dialog from closing when Escape is pressed.
  • Base styles and theming.
• List and List Item
  • Added missing styles for slotted igc-icon in the list item.
  • Icon and icon button sizes for the Indigo theme.
• Mask Input
  • Auto-fill behavior for mask patterns with literals.
• Navbar
  • Icon and icon button sizes.
• Select
  • Color for outlined type.
• Tabs
  • Add active pseudo-elements backgrounds for the active tab in Material theme.
  • Take scale factor when positioning the active tab indicator.
  • Selected indicator alignment.
• Tooltip
  • Do not show the tooltip when the tooltip target is clicked.
  • Removed the max-width constraint for slotted content.

IgxOverlayService

• IgxOverlayService.createAbsoluteOverlaySettings - Added a new overload accepting useContainerStrategy?: boolean as the second parameter. When true, uses ContainerPositionStrategy; otherwise defaults to GlobalPositionStrategy. The previous overload accepting outlet?: IgxOverlayOutletDirective | ElementRef is still supported but deprecated.

IgxSnackbarComponent, IgxToastComponent

• Added a new positioning input property. When set to container, the components is displayed inside its nearest positioned ancestor in place of the now deprecated outlet property.

IgxCombo, IgxSimpleCombo

• Introduced the selectionChanged event for both components. The event is not cancelable and is emitted after the selection is committed and the component state is updated.
• Added disableClear input that allows hiding the clear button even when items are selected. Defaults to false.

IgxOverlayService

• Deprecation - The outlet property in OverlaySettings, IgxOverlayOutletDirective, and igxToggleOutlet input on IgxToggleActionDirective are deprecated and will be removed in a future version. As overlay service now integrates the HTML Popover API and prefers rendering content in place / in the top layer, significantly reducing the need for outlet containers, new code should rely on the default in-place / top-layer rendering behavior instead of custom outlet containers.

AI-Assisted Development - Copilot Skill: Generate from Image Design

• Added a new igniteui-angular-generate-from-image-design Copilot Skill that teaches AI coding assistants/agents (e.g., GitHub Copilot, Cursor, Windsurf, Claude, JetBrains AI, etc.) how to implement Angular application views directly from design images (screenshots, mockups, wireframes).
• The skill provides a structured workflow covering image analysis, component discovery via MCP tools (list_components, get_doc), theme generation (create_palette, create_theme, create_component_theme), layout implementation, and visual refinement (set_size, set_spacing, set_roundness).
• Includes reference files:
  • Component Mapping - Maps common UI patterns (dashboards, charts, forms, navigation, data display, gauges) to the most appropriate Ignite UI for Angular component with key properties and decision rules.
  • Gotchas - Documents known pitfalls, component-specific constraints, and corrective patterns to help AI agents avoid common implementation mistakes.

AI-Assisted Development - Copilot Skills improvements

• igniteui-angular-grids skill - Added a new sizing.md reference covering grid and column width/height inputs, percentage and auto sizing modes, column sizing (minWidth, maxWidth, * star-sizing, auto-fit), and cell spacing/density control.
• igniteui-angular-components skill - Corrected Financial Chart (IgxFinancialChartComponent) documentation: updated chartType enum values to Auto, Candle, Line, Bar, Column to match the actual FinancialChartType API.
• igniteui-angular-theming skill - Minor cleanup to remove stale internal contributing reference.

• Icon service
  • Browser Safari: Now uses a plain Map instance for synchronizing state between actors. Since Safari does not support extended Map instances, it is required to use a plain Map for message transfer.

• IgcDataPieChart
  • DataPieChart - missing styling properties for the Others Slice.
• IgcDataTooltipLayer
  • TitleTextColor is overriden when chart's TitleTextColor is used.
• Excel
  • Fixed Excel Formula parser - Workbook.Load() throwing a Excel.FormulaParseException.
  • Object's Formulas are not round-tripped - Added Excel support for round tripping the camera tool.
  • Saving a VBA Signed Excel file does not keep a signature/certificate.

• AI-Assisted Development - Copilot Skills
  • Four end-user skills are now shipped with the igniteui-react package under the skills/ directory providing step-by-step guidance to GitHub Copilot and other LLM agents for common tasks:
    • igniteui-wc-choose-components - Identify the right component for a given UI pattern.
    • igniteui-wc-integrate-with-framework - Set up and use components in React, Angular, Vue, or vanilla JS.
    • igniteui-wc-customize-component-theme - Apply custom styles via CSS custom properties, parts, and the theming system.
    • igniteui-wc-optimize-bundle-size - Reduce production bundle size through selective imports and lazy loading.
• Chat
  • adoptRootStyles can now be toggled on/off at runtime.
• grid, IgrTreeGrid, IgrHierarchicalGrid, IgrPivotGrid
  • Improved performance by dynamically adjusting the scroll throttle based on the data displayed in grid.
• PDF export
  • Added PDF export functionality allowing users to export grid data to PDF format.
• Popover API
  • Dropdown menus and dialogs are now using HTML Popover API to provide better positioning and accessibility.
• Localization(i18n)
  • grid, IgrTreeGrid, IgrHierarchicalGrid, IgrPivotGrid, IgrCombo, DatePicker, IgrDateRangePicker, IgrCalendar, IgrCarousel, IgrChip, IgrInput, IgrTree
    • New Intl implementation for the grid components that format and render data like dates and numbers. Updated Intl implementation for IgrCalendar, DatePicker, and IgrDateRangePicker.
    • New localization implementation for the currently supported languages for all components that have resource strings in the currently supported languages.
    • New public localization API and package named igniteui-i18n-resources containing the new resources that are used in conjunction.
• Breaking Changes
  • Themes
    • Changed global prefixes for CSS custom properties for component themes to align with other Ignite UI component libraries.
  • Chat
    • Removed the typingIndicator template renderer. Use the typing-indicator slot instead.
  • Tooltip
    • Removed the disableArrow deprecated property.
  • Library
    • Minimum Node version required is now >= 22.
  • grid, IgrTreeGrid, IgrHierarchicalGrid, IgrPivotGrid
    • Original data array mutations (like adding/removing/moving records in the original array) are no longer detected automatically. Components need an array reference change for the change to be detected.

• Carousel
  • Error with context instantiation.
• Combo
  • Fixed cursor style over non input parts.
• Textarea
  • Fixed cursor style over non input parts.

• AI-Assisted Development - Copilot Skills
  • Four end-user skills are now shipped with the package under the skills/ directory. They provide step-by-step guidance to GitHub Copilot and other LLM agents for common tasks:
    • igniteui-wc-choose-components - Identify the right component for a given UI pattern.
    • igniteui-wc-integrate-with-framework - Set up and use components in React, Angular, Vue, or vanilla JS.
    • igniteui-wc-customize-component-theme - Apply custom styles via CSS custom properties, parts, and the theming system.
    • igniteui-wc-optimize-bundle-size - Reduce production bundle size through selective imports and lazy loading.
  • To enable the skills in your project, copy the skill folders into your repository's .github/skills/ directory so Copilot can automatically discover them.
• Library
  • Minimum Node version required is now 22 or above.
• Themes - Breaking change
  • Changed global prefixes for CSS custom properties for component themes to align with other Ignite UI component libraries.
• Chat
  • Removed the typingIndicator template renderer. Users can use the typing-indicator slot instead.
  • Removed the disableArrow deprecated property.

• Carousel
  • Context instantiation issue.
• Combo and Textarea
  • Corrected cursor style over non input parts.

• Data Chart
  • Added OthersCategoryBrush and OthersCategoryOutline to DataPieChart and ProportionalCategoryAngleAxis.
• Radial Chart
  • Added a check for bucket size equals to 0.

• Layouts
  • Skip resolving property editor props containing 'constantValues'.
• Data Chart
  • Syntax error while building infragistics.dvcommonwidget.js.
  • infragistics.dvcommonwidget.js has "unser" typo instead of "unset" in case names.
  • Fixed GetCategoryIndexAxis() for annotation layers.
• Data Pie Chart
  • SeriesPointerMove event doesn't fire correctly when StartAngle is set.
• Excel
  • Workbook.Load() throwing a Excel.FormulaParseException.

• Calendar
  • Fixed the 'aria-hidden' attribute logic for calendar weeks in a 'perfect month' (a month where all weeks are fully contained within that month). Previously, the attribute was only applied to edge weeks (first and last). Now it applies to any week where all days are hidden.
• Date picker
  • Fixed error with CSS border for slotted actions in dialog mode.
• Input
  • Fixed problem with placeholder color on focus.
  • Fixed issue with CSS border when suffix slot content is present.
• Textarea
  • Align bottom padding to the design system - fixed.
• Validation
  • Fixed bug with slotted validation text following current theme.

• Added Theming Scoping Container
  • The 'igc-theme-provider' component allows you to scope themes to specific parts of your page using Lit's context API. This enables having multiple different themes on the same page.
  • Works both in Shadow and Light DOM.

• Tile Manager
  • Header is hidden only when there is no content and maximize/fullscreen are disabled.
• Theming
  • Fixed to resolve initial theme based on document computed styles rather than stylesheets.

• Added Theming Scoping Container
  • The 'igc-theme-provider' component allows you to scope themes to specific parts of your page using Lit's context API. This enables having multiple different themes on the same page.
  • Works both in Shadow and Light DOM.

• Tile Manager
  • Header is hidden only when there is no content and maximize/fullscreen are disabled.
• Theming
  • Resolve initial theme based on document computed styles rather than stylesheets.