Thank you! Let us know if you find any bugs or have any suggestions.
On a side note, we were really torn on whether to use favicons or tab screenshots as the node images. If anyone has design opinions on this, we'd love to hear them!
Browser history uses favicons, but I think I would go with tab screenshots. In your browser history, because everything is collapsed into a line, it's harder to parse a logical grouping, so having similar favicons helps. But in Visual History, because the history is tab specific, you don't have that problem. You are more likely to need to differentiate between different pages on the same site, making favicons less useful.
Regardless, this is really cool, and I'll definitely be sharing it.
... Also, I just realised it overrides cmd+arrow keys. Those are super important for navigating in text on OS X! Unfortunately I'll have to disable until it doesn't do that, since there doesn't seem to be an option to remap or disable those keybinds.
I think that with sufficient determination I could have pushed it through, but it was a side project, I was a junior engineer, & I would have needed significant design resources & buy-in to get it to shippable. I believe it would have been possible (Chrome is an especially open & flat structure within google, compared to e.g. Android), but I wasn't willing to go through the effort at the time. I ended up leaving Google to be one of the first engineers at Transcriptic :)
On a side note, we were really torn on whether to use favicons or tab screenshots as the node images. If anyone has design opinions on this, we'd love to hear them!