4 ms·
History in browsers and editors should absolutely be a trer so we can do changes without the risk of losing a state we want. If you undo/go back and then make s
by Zalastax 10y ago
History in browsers and editors should absolutely be a trer so we can do changes without the risk of losing a state we want. If you undo/go back and then make some change it's often impossible to reach back to before the undo. Why is history as a tree not a more common feature?
- agumonkey 10y agoEmacs has an undo tree and it can be confusing, maybe browser devs tried and it ended up the same way. Now I don't advocate for it to be an average main feature, but an opt-in or plugin would be awesome. It's on my dillo patch TODO list for a year.