Rails - Jul 2005 - error_messages_for and the dreaded Back button

I''m trying to come up with a non-crazy way to
''de-error-tize'' a page
when the user arrives there via the Back button.
I showed the users what I''ve gotten working so far, and they
wouldn''t
stop talking about how the messages were still there when you hit Back.

I tried explaining that the server doesn''t see a new request when you 
hit that button, but it didn''t take.  I can''t just do an
onLoad
function, because it needs to know whether we''re legitimately 
redisplaying the page to show errors, or whether we''ve gotten here via 
''Back''.

Has anyone worked around something like this?

--Wilson.

On 7/19/05, Wilson <defiler-ifvz4xmYPRU@public.gmane.org>
wrote:
> I''m trying to come up with a non-crazy way to
''de-error-tize'' a page
> when the user arrives there via the Back button.
> I showed the users what I''ve gotten working so far, and they
wouldn''t
> stop talking about how the messages were still there when you hit Back.
> 
> I tried explaining that the server doesn''t see a new request when
you
> hit that button, but it didn''t take.  I can''t just do an
onLoad
> function, because it needs to know whether we''re legitimately
> redisplaying the page to show errors, or whether we''ve gotten here
via
> ''Back''.
> 
> Has anyone worked around something like this?
Since you''d be fighting against standard browser behavior,
it''s going
to be a wacky workaround.  Try doing something with a cookie?  Posting
the form sets a cookie value.  Some javascript looks for the cookie,
and either deletes it, or performs a fresh load of the form if it''s
not there.

This is a similar approach to how Flickr solves the caching issue on
pages that have been modified by ajax:
http://www.ajaxian.com/archives/2005/05/ajax_summit_eri.html


-- 
rick
http://techno-weenie.net