Reloading ContentEditable area when visitor clicks on back button

[Jason]

I'm building a rich editor to replace a textarea, and am about to
release it as "live." But there's one last thing I want to do with it.

When using a textarea, if the visitor clicks on "back" then the
information is (usually) still there. But with the contenteditable
field, it's gone.

I read on a web page a few days ago that there was an easy solution to
this, but I didn't save the information and didn't save the page. Any
ideas?

TIA,

Jason
<note>I originally posted this to a DHTML ng a week ago, but it's a
low-activity ng and no one has replied. I've had excellent advice in
CLJ before, so I'm hoping you guys will forgive me that this is
slightly off topic.</note>

[David Mark]

On Jul 29, 10:25 pm, Jason <[e-mail]:

I'm building a rich editor to replace a textarea, and am about to
release it as "live." But there's one last thing I want to do with it.

When using a textarea, if the visitor clicks on "back" then the
information is (usually) still there. But with the contenteditable
field, it's gone.

Right.

>
I read on a web page a few days ago that there was an easy solution to

Every time a change is made, update a hidden form field. Then in the
window onload event, insert the contents of that field into the
editable element.

this, but I didn't save the information and didn't save the page. Any
ideas?

Post a URI so I can look at it. I may have some additional
suggestions. Last I saw it, the feature detection portion needed
work.

[Jason]

Post a URI so I can look at it. I may have some additional

suggestions. Last I saw it, the feature detection portion needed
work.

Remember that this is a Perl script, so there are some things going in
the background that you don't see client-side:

http://www.gowilkes.com/cgi-bin/beta.cgi

I'm still using the oDiv dummy field because I couldn't get the one
that you posted before (to test the body) to work.

I've had a lot of people (both techies and non-techies) to help beta
test it on my site, and the only problem I've had is that one person
tried to submit a reply, but it gave him an error that there was
nothing in the comments field. He tried to reply again, and it went
through. I haven't been able to duplicate that error, though, and no
one else has reported it.

Thanks, David,

Jason