Native Undo History

[johanneswilm]

@dmonad

Though at this time browsers don’t fire historyUndo when the undo stack is empty. So with this approach, we would also need to find a method to tell the browser to actually fire undo/redo events if the stack is empty.

Absolutely. The two would go hand in hand: enable the button and fire the event. events should usually also fire even if the browser itself would not make any change to the DOM. Its meant as a “The user has expressed the wish to do X” even if the browser thinks that wish is impossible to fulfill at times.

@dmonad

I proposed to work with the undo stack, because I thought it would work better with the existing implementation. But in the end I wouldn’t mind either of the approaches as long as I can manipulate the scope and state of undo / redo buttons.

Same here. I think the best is simply to present a number of different ideas to the browser makers which require different levels of commitment on their part.