UndoManager's redo stack is not being reset after a new change
Created by: tbastos
Correct behavior for the UndoManager would be to clear the redo stack once a new change (i.e. any changeset that's not an undo) is made.
We should add a test case to the test suite.
How to replicate the problem:
- Change field from state A to state B.
- Undo change.
- Change field from state B to state C.
- Redo change. Field returns to state B, the user's change is lost.
Reported by @xvaldetaro