Yes. Managing that stupid history state is the part the took an hour (but AKAICT it’s working perfect now).
I originally wanted to do something similar with the [next] button, and have the state handler actually check where “next” was in relation to the current branch, but since it only ever goes to one place I just fudged and made it always go to the “fork.” I don’t think it would be too difficult to make this change in the future, if we wanted to make a general-purpose form tree.
I know but I didn’t feel the need to prefix it for dev …
I prefer doing JS dev in chrome and for a while I thought I had screwed something up because the form kept pushing itself off the screen : )