Skip to main content

Current limitations

The current feature surface is broad, but the following constraints should be evaluated before adoption.

Not currently implemented​

  • Variable or automatic row heights and text wrapping
  • Master/detail row panels
  • Pivoting on the server-side row model (client-side pivot is supported)
  • Within pivot mode: filters on the generated columns (filters run pre-pivot on source rows), in-table row/column grand totals (the footer aggregate row shows per-column grand totals), and drag-and-drop between the column panel's field wells (well editing is click/keyboard)
  • ARIA exposure of the column-group header hierarchy (parent header cells are presentational; leaf headers are full columnheaders)
  • An in-grid contextual keyboard-shortcut reference

The grid's assistive-technology support — the ARIA grid model, focus and announcement behavior, and its current boundaries — is described on the dedicated accessibility page.

Client-side-only behavior​

Quick filter, tree data, full-width rows, custom filter matchers, and row transactions require the client-side model. Server-side grouping and sticky group rows are supported, but server-side group sorting is local to each listing.

Server-side differences​

The server is responsible for filtering and sorting complete data. As a result, iteration cannot expose a separate pre-filter/pre-sort universe. Open-ended listings have provisional row/page counts until a short block establishes the end.

Layout​

All rows currently have one fixed height. Cell spans stop at pinned-section boundaries. A span that exists only on some rows can produce a visually non-rectangular selected region even though the selection model remains a rectangle.