>I see from other posts on this thread that the user may have added multiple content. In that case it seems to me that you would need to store the current html (or serialized DOM) when the user navigates away from the page and then restore it on return.
>
>You could keep this in local or session storage or, for HTML5, use pushstate() (or replacestate()) and popstate()
>
>See HTML5 history object : https://developer.mozilla.org/en-US/docs/Web/Guide/API/DOM/Manipulating_the_browser_history

That would be interesting to consider. Thanks for the reference