Opened 9 years ago
Last modified 9 years ago
#25026 closed New feature
Should QueryDict accept "html json forms"? — at Initial Version
| Reported by: | zauddelig | Owned by: | nobody |
|---|---|---|---|
| Component: | HTTP handling | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
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']}>