Rajesh -- THANK YOU very much! you are correct. My issue was not on the <a> side -- it was on the target side -- i had a typo that was messing up the text of the id="". Once that was fixed, it worked exactly as you said it should; this was a PIBKAC issue.
I did however learn something: I was not aware of the distinction between browser/server functionality in resolving local links...of course it seem obvious to me now. On Dec 5, 11:58 am, Rajesh Dhawan <[EMAIL PROTECTED]> wrote: > On Dec 5, 2:41 pm, PFL <[EMAIL PROTECTED]> wrote: > > > Thanks for your replies --I am still stuck here. > > > >Have a look in the output from the development server - I very much doubt > > >that the click results in any request being sent. > > > A request is definitely sent for each of these cases: "/doc/", "/ > > doc#", "/doc#1/". I can see each of these generating a hit on the > > local dev server standard out. > > But you omitted the one that your template is actually resulting in: > > /doc/#1 > > Incidentally, they will all generate a hit if you punch them into your > browser's URL bar. The # anchor implementation is a browser feature > not a web server feature. So, the way to test whether a new link is > being generated is to use your browser like this: > > First point your browser to /doc/ to get Django to serve your request. > Now, click on the anchor link in your browser. You should not see a > new web server request resulting from that click. Your browser should > simply pan you down to where you have the element with id=1. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
