This is an intersting problem though. Without the ability to edit the HTML, a page refresh is going to kill any work you did.

Granted, in most cases, the need for a page refresh would not matter, as the browser is going to drop the input form data anyway.

One advantage would be you could potentially store the form data.

As web apps become more complex, it may not be form data, but positioned elements.

What is the best way to save this state in hopes of protecting the user from a refresh? Is it even worth it?

I can see three ways. Local browser data store, not currently supported by all browsers.

Second is appending to a refresh link, or the URL directly, some data that can store the last state.

Third is use of cookies to store state.

Curious what others chose to use in solving this, or if it is even something considered a problem worth solving.

--
Scott
Iphone says hello.

On Sep 2, 2009, at 7:29 PM, "Rick Faircloth" <r...@whitestonemedia.com> wrote:

Thanks for the reply, Ricardo...

After thinking about it, it really doesn’t matter if the HTML is cha nged.
It'll process fine, as you said.

What I was really trying to avoid was a problem with the newly entered
data being removed if I focused on the field with the cursor again.

I came up with a better solution that deleted the error message I put
into the field, but didn't delete the new typed in code.

Reply via email to