I was thinking about using that same library and gave up on the whole idea because of the emailing links problem and just went back to reloading the whole page. The URL changes and the content changes. IMHO that is the "more native" approach. The history.js approach is full of difficult problems such as emailing a link to someone that does not run javascript. Perhaps you don't care about that edge case but I decided it was better to concentrate on making the whole page load faster than solving all the AJAX history problems. That said I do see the appeal and if everything supported the HTML 5 way I might feel differently. I'm not knocking history.js and I think #state is a cleaver hack but if the goal is to email links I think reloading the whole page is the only solution.
-- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry5-Anchor-Usage-for-Navigation-tp5036547p5036735.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
