Repository navigation

Issues

IUndoRedoProvider.StateChanged handlers run while the stack's lock is held, so a handler that marshals to the UI thread (Dispatcher.Invoke) deadlocks against a UI-thread read of Current/CanGoBack
ktsu-dev/Navigation#90 · opened on Oct 19, 2026
1
Stacks sharing a SimpleUndoRedoProvider (the NavigationStackFactory default) lose undo entries or throw NullReferenceException under concurrent navigation
ktsu-dev/Navigation#89 · opened on Oct 18, 2026
1
NavigationState.FromNavigationStack throws ArgumentOutOfRangeException (or records the wrong position) while another thread navigates or clears
ktsu-dev/Navigation#88 · opened on Oct 17, 2026
1
Navigation is pinned to the retired ktsu.UndoRedo.Core 1.1.4, and moving to ktsu.UndoRedo 3.x makes a failed undo re-run an unrelated action (tests stay green)
ktsu-dev/Navigation#82 · opened on Oct 6, 2026
1
docs/ examples don't compile: they use NavigationFactory, CreateNavigation<T>, FromNavigation and NavigationEventHandler<T>, none of which exist
ktsu-dev/Navigation#78 · opened on Oct 5, 2026
1
Stacks from NavigationStackFactory, even with a persistence provider, return INavigation<T>, which has no Save/Load methods, so persistence needs a downcast
ktsu-dev/Navigation#76 · opened on Sep 30, 2026
1
When a NavigationChanged handler throws during Undo, the stack is already undone but the provider records the action as not undone, so Redo is disabled
ktsu-dev/Navigation#75 · opened on Sep 30, 2026
1
NavigateTo copies the whole history on every call, even with no undo provider; with an undo provider each retained action keeps two full snapshots (O(n) per navigation, ~125 MB at 50k entries)
ktsu-dev/Navigation#72 · opened on Sep 29, 2026
1
A cancelled or interrupted SaveStateAsync truncates the state file and destroys the previous save; HasSavedStateAsync then says true while LoadStateAsync returns false
ktsu-dev/Navigation#71 · opened on Sep 29, 2026
1