#25026: Should QueryDict accept "html json forms"?
-------------------------------+--------------------------------------
Reporter: zauddelig | Owner: nobody
Type: New feature | Status: new
Component: HTTP handling | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by zauddelig):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Old description:
> On 23 may 2014 W3C published this working draft:
> http://www.w3.org/TR/html-json-forms/
>
> I'm focusing the attention on this paragraph:
>
> >User agents that implement this specification will transmit JSON data
> from their forms whenever the form's enctype attribute is set to
> '''application/json'''. During the transition period, user agents that do
> not support this encoding will fall back to using '''application/x-www-
> form-urlencoded'''. '''This can be detected on the server side, and the
> conversion algorithm described in this specification can be used to
> convert such data to JSON'''.'
>
> Should Django QueryDict support this transition period and return data
> structures?
>
> Here are some examples on how QueryDict should behave following the
> working draft:
>
> {{{
> >>> QueryDict("a=1&a=2") # classical behavior
> <QueryDict: {u'a': [u'1', u'2']}>
> >>> QueryDict("a[0]=1&a[1]=2") # the new behavior
> <QueryDict: {u'a': [u'1', u'2']}>
> }}}
New description:
On 23 may 2014 W3C published this working draft:
http://www.w3.org/TR/html-json-forms/
I'm focusing the attention on this paragraph:
>User agents that implement this specification will transmit JSON data
from their forms whenever the form's enctype attribute is set to
'''application/json'''. During the transition period, user agents that do
not support this encoding will fall back to using '''application/x-www-
form-urlencoded'''. '''This can be detected on the server side, and the
conversion algorithm described in this specification can be used to
convert such data to JSON'''.'
Should Django QueryDict support this transition period and return data
structures?
Here are some examples on how QueryDict should behave following the
working draft:
{{{
>>> QueryDict("a=1&a=2") # classical behavior
<QueryDict: {u'a': [u'1', u'2']}>
>>> QueryDict("a[0]=1&a[1]=2") # the new behavior
<QueryDict: {u'a': [u'1', u'2']}>
>>> QueryDict("a[0]=1&a[1]=2") # proposed to fix behavior
<QueryDict: {u'a[0]': [u'1'], u'a[1]': [u'2']}>
}}}
--
--
Ticket URL: <https://code.djangoproject.com/ticket/25026#comment:1>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.32da0b7f399d3f581a0ffdb97a1f3380%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
