#16796: isMobile() should be added to request objects
-------------------------+-------------------------------
Reporter: anonymous | Owner: nobody
Type: New feature | Status: new
Milestone: | Component: Uncategorized
Version: 1.3 | Severity: Normal
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------+-------------------------------
Currently, in Django one needs to use a custom middleware to handle
template switching logic for mobile view presentations. Here's my
suggestion, since knowing whether a user is_mobile() is kind of a common
scenario, or should be in modern web development, is it appropriate to add
this be added to Django out of the box? There's a debate whether to do
this in the user agent handling, however, it seems it might the most
appropriate for our concerns. Here's two different custom middlewares that
might be a good candidate examples for how to handle this for
http://djangosnippets.org/snippets/2001/ or
http://djangosnippets.org/snippets/2033/
--
Ticket URL: <https://code.djangoproject.com/ticket/16796>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en.
