Ahh okay, Then yeah, something similar to the messages framework may work well for you in this case. You could even use the messages framework directly in a "hackish" sort of way just by putting some code in your template that looks for a Messages Warning and spits out javascript accordingly. Shouldn't take but 15 minutes to implement.
On Thu, Aug 2, 2012 at 12:17 PM, Larry Martell <larry.mart...@gmail.com>wrote: > On Thu, Aug 2, 2012 at 9:24 AM, Kurtis Mullins <kurtis.mull...@gmail.com> > wrote: > > Sorry I didn't catch this part. You could modify your "Login" view to > check > > the user agent and if it's an incompatible browser, and simply return a > > template that tells them their browser is unsupported. I'd do this before > > they even hit the Login Form just to be courteous to the user. But this > > modification would to be done in the Login view or whichever view(s) > present > > the Login Form. > > > > If you want to implement this site-wide, simply make your own custom > > middleware that looks for this user agent and display the fore-mentioned > > template. > > > > The JavaScript idea mentioned by Andreas would be a great solution as > well. > > The want the user to be able to continue to use the app. The popup is > just to advise them that some features may not work. So I have to > still pass them through to whatever they're getting redirected to, and > not just stop. > > > > > > > On Thu, Aug 2, 2012 at 11:13 AM, Andreas Schosser <a...@state-of-mind.de> > > wrote: > >> > >> Hi Larry > >> > >> > They want the dialog to pop up on top of the login screen before the > >> > redirect. I don't know where the code that does this would live or how > >> > it would get invoked. > >> > > >> > As far as to why they want this, it doesn't really support IE, and > >> > they want to alert the user to that if that's what they're using. It's > >> > a custom app, not for public use. > >> > >> So why don't you catch the form.submit event with JavaScript and notify > >> the user about any issues with his browser. > >> Then you could either prevent them from proceeding or call the > >> form.submit within your JavaScript code. > >> > >> No server side logic is necessary but of course it only works with > >> JavaScript enabled. > >> > >> Greetings > >> Andreas > >> > >> -- > >> state of mind () > >> > >> http://www.state-of-mind.de > >> > >> Franziskanerstraße 15 Telefon +49 89 3090 4664 > >> 81669 München Telefax +49 89 3090 4666 > >> > >> Amtsgericht München Partnerschaftsregister PR 563 > >> > >> -- > >> 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 > >> django-users+unsubscr...@googlegroups.com. > >> For more options, visit this group at > >> http://groups.google.com/group/django-users?hl=en. > >> > > > > -- > > 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 > > django-users+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/django-users?hl=en. > > -- > 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 > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
