On Friday, November 28, 2014 11:17:15 AM UTC+1, Jorge C. Leitão wrote: > > IMO, this lies on the assumption that the Form's field names are never > shown to the user. When the form is POST, this assumption is valid. > However, in a GET, the field names are presented in the URL, and the > assumption breaks. This even exposes serve-side implementation details (the > field name of the Form) to the user. >
You always expose some server information, even with POST -- you just don't see the parameters in the URL > 1. how common is this? > No idea on that, but field names are programmatic identifiers (as you said, they are an implementation detail), translating those will break loads of things. > 2. wouldn't it add a lot of complexity to JavaScript and CSS, specifically > on name selectors? > They wouldn't work anymore unless you send a mapping to the client, again exposing server implementation details. > 3. do any other web framework support this? > Not that I am aware. Could we have some feedback to decide wether it justifies or not to have > this in Django? > Personally, I am against it, I don't think that the gains justify the effort. Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c3258005-6bac-483f-b425-2681b8898b34%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
