🏠 back to Observable

The History feature usage is not very obvious.

#1

This is a simple thing: trying to find how to revert to a specific history version should be obvious, but it’s not:

  • It’s hidden in a separate menu that’s not obviously related (aside from that being how you get to History in the first place)
  • The last time you saw that menu, the relevant item wasn’t even there, so you think you’ve already ruled it out.
  • The Exit button seems like the only available candidate—but that’s not it, and you’re back to where you started from.

There are a lot of ways you could fix this, but something visible and local to the history, please.

I think I’ll finally remember how now, but I went through several iterations of confusion before it stuck.

#2

It’s a great feature but I think the affordances could use some work - my biggest issue is that I tend to accidentally start editing previous history states and then lose the work

1 Like
#3

Thanks for the feedback @BobKerns, @Job — we agree! I’ve updated a couple of internal tickets with these requests.

1 Like
#4

Two ideas in this area:

I’ve often found myself wanting to quickly go through the shared versions in history, because they’re usually some kind of interesting points (new features, crushed bugs, and more stable than the states in between shares).

I’m very much missing some kind of annotation or labelling (like git commit messages), so that the history could be searchable and more meaningful than “Edited A / Edited A / Edited B…”.

5 Likes
#5

One thing I don’t know how to do from the UI is see a diff between two versions. The only way I have figured out is to construct the URL for it manually.

You folks may want to look at Wikipedia’s history view for ideas. https://en.wikipedia.org/w/index.php?title=D3.js&action=history

1 Like