Supporting history of UI actions for undo/redo is mostly a hack right
now. What we really need is for the browsers to provide native support
for maintaining sub-page history changes. Maybe these folks will save
the day:
http://www.w3.org/2006/rwc/
To fix the problem you're observing, or at least mitigate it, we could
potentially use a cookie to store the last state of the exhibit as well
as a limited stack of past UI actions. This will require changing the
Exhibit code base, and I'm not sure when I'll be able to get to it.
To temporarily fix the problem for your own site, you may want to
consider using those lightbox / thickbox / or whatever it's called
technique to avoid navigating away from the exhibit page. For entirely
external links, consider opening a different tab. It's not the ideal
solution, I know.
David
Kevin Smith wrote:
> It's quite amazing that history works. By implementing the
> __history__.html file, when a facet selections are clicked, a user is
> able to use the back button to go back to a previous selection.
>
> What puzzles me is that when a non-facet link is clicked, like to a
> detail view page, the user can't click back? I imagine there is an event
> listener or hook firing off that I'm not aware of?
>
> Best regards,
>
> Kevin Smith
> Director of New Media
> Monterey County Weekly
> _______________________________________________
> General mailing list
> [email protected]
> http://simile.mit.edu/mailman/listinfo/general
>
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
