On 04.01.2013 17:43, Thiago H de Paula Figueiredo wrote: >> Is there a "best way" to store changes made by AJAX requests in the page? > Have you tried non-flash session persistence
This would break tabbed browsing. If I change the selection in one tab, the search field in a second tab will also act differently. > and setting the field to null after you don't need it anymore? Even if I ignore the confusion with tabbed browsing, I am not sure how to detect that the search field is not needed anymore. If a user does not click on a search result but on another navigational element instead, the field would still be persisted. Would it be possible to add the selection to the URL of the page containing the search field? I am not sure about changing the activation context with AJAX calls. Regards Stephan
smime.p7s
Description: S/MIME Kryptografische Unterschrift
