ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #primeng
Issue Overview The PrimeNG DataTable component supports virtual scrolling to handle large data sets efficiently. When selectionMode="multiple" is enabled, the documentation states that selected rows should remain selected even when they scroll out of the visible buffer. However, in practice, the component appears to clear the selection once the virtual scrol
When implementing a p-table for datasets that may scale from a few hundred to several thousand records, there is a trade-off between initial load latency and per-page interaction speed. Client-side pagination loads the entire dataset into browser memory, enabling instantaneous transitions. However, this approach risks UI freezing or heap memory exhaustion as
Context PrimeNG's p-table component supports lazy loading through the [lazy] input and (onLazyLoad) event emitter. When enabled, the component delegates data fetching to the application, passing a LazyLoadEvent object containing first (offset) and rows (page size) values. The integrated p-paginator updates these values automatically on user interaction. Unre
Integration of PrimeNG Table with Mocked HTTP Services When integrating the p-table component with Angular's HttpClientTestingModule , developers typically use the [lazy] input to trigger data fetching via the onLazyLoad event. This allows the UI to be tested against mock observables without requiring production credentials or a live backend. A specific chal
Goal Render a PrimeNG p-table with virtualScroll enabled inside an Angular component using ChangeDetectionStrategy.OnPush. Data updates arrive asynchronously and replace the value input with a new array reference. Constraint PrimeNG documentation does not explicitly confirm OnPush compatibility for virtual scroll. The table tracks rows through IterableDiffer
Goal Ensure that when a child Dialog is closed, focus returns to the element that opened the parent Dialog, satisfying WCAG 2.4.3. Current Behavior PrimeNG v18 captures the active element at Dialog open time. In nested scenarios, the captured element is the child Dialog’s trigger, not the parent’s trigger button. Closing the child leaves focus on the parent
angular