Issues

SaveStateAsync resets a chmod 600 state file to 0644 and replaces a symlinked state file with a regular file (regression from the temp-file save, #105)

ktsu-dev/Navigation#107 · opened

on Nov 5, 2026

1

Two concurrent first saves to a new state file throw IOException "The file '…/state.json' already exists"

ktsu-dev/Navigation#106 · opened

on Nov 4, 2026

1

Concurrent NavigateTo calls can raise NavigationChanged out of order, so a subscriber tracking e.CurrentItem ends on a different page than stack.Current

ktsu-dev/Navigation#104 · opened

on Nov 2, 2026

2

Undo still wipes the redo history when a NavigationChanged handler navigates a second stack sharing the provider (#95 only guards the stack being undone)

ktsu-dev/Navigation#101 · opened

on Oct 31, 2026

1

JsonFilePersistenceProvider silently drops NavigationItem subclass properties and restores plain NavigationItems

ktsu-dev/Navigation#97 · opened

on Oct 29, 2026

1

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

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

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