That's understandable. However, *client-side* part of Tapestry might deal with URL anchors in one way or another, for example, transforming them to some kind of component events being sent to server over AJAX.
This is actually what I'm interested in: to create some kind of 'bridge' between browser history events and Tapestry server-side events. On Sat, Oct 26, 2013 at 5:06 PM, Dmitry Gusev <dmitry.gu...@gmail.com>wrote: > Please note: > > Anchors or URL fragments as they are referred to in RFC > 1738<http://www.ietf.org/rfc/rfc1738.txt>, > > are not sent by the client to the server, when requesting for a resource. > > > > > So dealing with anchors is completely client-side job. > > Of course you can redirect from server-side to anchored URL. > > > > On Sat, Oct 26, 2013 at 6:54 AM, Ilya Obshadko <ilya.obsha...@gmail.com > >wrote: > > > Found this thread while looking for a similar solution. > > > > - I'm using AJAX calls heavily and still want to be able to represent > each > > page state as a separate URL. > > - I need to use anchor part of the URL in page activation handlers > > > > Is there any proper way to do that in 5.4? > > > > > > > > On Thu, Dec 1, 2011 at 8:04 AM, trsvax <trs...@gmail.com> wrote: > > > > > 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 > > > > > > > > > > > > -- > > Ilya Obshadko > > > > > > -- > Dmitry Gusev > > AnjLab Team > http://anjlab.com > -- Ilya Obshadko
