Re: [Django] #25026: Should QueryDict accept "html json forms"?

[Django]

#25026: Should QueryDict accept "html json forms"?
---+--
 Reporter:  zauddelig  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:  needsinfo
 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 timgraham):

 * status:  new => closed
 * resolution:   => needsinfo


--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.4410868e500429b60534b5fd4fa32846%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25026: Should QueryDict accept "html json forms"?

[Django]

#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
---+--

Comment (by timgraham):

 I'm not sure what you meant by that last comment. Was it a reply to my
 comment or something unrelated?

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.a4862cb8e980db883b21aead228b5973%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25026: Should QueryDict accept "html json forms"?

[Django]

#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
---+--

Comment (by zauddelig):

 The draft was misinterpreted as a compliant client POST data would be
 found in request.body not in request.POST.

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.d19ac10705eb90ebe8aaeba1da344792%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25026: Should QueryDict accept "html json forms"?

[Django]

#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
---+--

Comment (by timgraham):

 It may be a bit premature to implement functionality described in a
 working draft document. Can you provide any information about whether
 other projects are implementing its functionality?

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.dda05f2773abccd7c23d2fad27e01c2f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25026: Should QueryDict accept "html json forms"?

[Django]

#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=2")  # classical behavior
> 
> >>> QueryDict("a[0]=1[1]=2")  # the new behavior
> 
> }}}

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=2")  # classical behavior
 
 >>> QueryDict("a[0]=1[1]=2")  # the new behavior
 
 >>> QueryDict("a[0]=1[1]=2")  # proposed to fix behavior
 

 }}}

--

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
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.

[Django] #25026: Should QueryDict accept "html json forms"?

[Django]

#25026: Should QueryDict accept "html json forms"?
---+
 Reporter:  zauddelig  |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  HTTP handling  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 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=2")  # classical behavior
 
 >>> QueryDict("a[0]=1[1]=2")  # the new behavior
 
 }}}

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.a826e539394df100314394007bddcd84%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.