Chat: selectedIndexChange emits a number but onTabChange reads event.index #1019

New Issue

2026-08-12T08:11:39Z

spikerj commented

2026-08-12 08:11:39 +00:00

Summary

The chat template binds (selectedIndexChange) which emits a bare number, but onTabChange treats the argument like a MatTabChangeEvent and reads event.index. That clears/wipes selectedTabIndex and breaks history auto-load driven from the template binding.

Found by

Wave 6 coverage tick 9 a7 (bae903f1).

Expected

Either bind (selectedTabChange) and use event.index, or change onTabChange to accept number directly.

## Summary The chat template binds `(selectedIndexChange)` which emits a bare `number`, but `onTabChange` treats the argument like a MatTabChangeEvent and reads `event.index`. That clears/wipes `selectedTabIndex` and breaks history auto-load driven from the template binding. ## Found by Wave 6 coverage tick 9 a7 (`bae903f1`). ## Expected Either bind `(selectedTabChange)` and use `event.index`, or change `onTabChange` to accept `number` directly.

spikerj commented

2026-08-13 23:23:41 +00:00

Already present on spikersoft-angular master. onTabChange takes a number (matching selectedIndexChange), not event.index. Closing.

Already present on `spikersoft-angular` `master`. `onTabChange` takes a `number` (matching `selectedIndexChange`), not `event.index`. Closing.

spikerj closed this issue

2026-08-13 23:23:55 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#1019