id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
25026	"Should QueryDict accept ""html json forms""?"	zauddelig	nobody	"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']}>

}}}




"	New feature	closed	HTTP handling	dev	Normal	needsinfo			Unreviewed	0	0	0	0	0	0