Context Navigation

Changes between Initial Version and Version 1 of Ticket #4015

initial	v1
4	4
5	5	* If you use `django.contrib.auth.views.logout` and have it return a template directly, the template may "think" you're still logged in even though you aren't (because `request.user` is still a `User` object). Having it return a redirect instead shows the expected behavior, because it ends up generating a new request).
6		* If you use forms which subclass `django.contrib.auth.forms.AuthenticationForm` (e.g., the form for posting registered comments), the form may ~~think you're anonymous even after it's~~ logged you in (because `request.user` is still an `AnonymousUser` object). This is why, for example, entering a username and password when previewing a registered comment seems to do nothing (the form will still think those fields are required, because it doesn't know you've successfully logged in during that request).
	6	* If you use forms which subclass `django.contrib.auth.forms.AuthenticationForm` (e.g., the form for posting registered comments), the form may still think you're anonymous even after it's successfully logged you in (because `request.user` is still an `AnonymousUser` object). This is why, for example, entering a username and password when previewing a registered comment seems to do nothing (the form will still think those fields are required, because it doesn't know you've successfully logged in during that request).
7	7
8	8	Having `login` and `logout` update `request.user` would clear this up.