On Thu, 2009-07-16 at 16:00 +0000, Javier Guerra wrote: > On Thu, Jul 16, 2009 at 3:51 PM, Michael<[email protected]> wrote: > > This information isn't transmitted to the server in anyway so short of what > > you described above, Django can't really solve your issue. > > but where is it getting lost? i mean, what does the html looks like? > does it have the #section1 in the action attribute? i imagine three > answers: > > 1: no #section1 in the HTML => Django is losing it, should be fixed
Re-read the thread. The #part of the URL is not something ever transmitted beyond the browser. No web application ever sees the #part of a URI. > > 2: #section1 present, but not urlencoded => Django should encode it, > since it's a parameter for the view wrapper. > > 3: #section1 present and urlencoded => browser's fault, should be > worked around with JavaScript > Cheers Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
