-
-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AJAX field with the same name as persistent parameter behaves unpredictible #33
Comments
That's because in AJAX requires Nette does not differentiate between POST a GET parameters. |
Who requires it? Whether it is AJAX or not is irrelevant, isn't it? POST data should be separated from query string parameters. |
This is an issue of nette/application, not nette/forms, see here. @JanTvrdik: Is that in some RFC or something? |
@JanTvrdik I can't find any material about joining GET and POST parameters in AJAX. Can u please provide some link? |
@fprochazka: I already provided link to that, but @JanTvrdik should provide reference for "AJAX requires Nette". I don't think AJAX requires such thing in any way. |
@Majkl578 that was most likely typo and I don't see how bashing @JanTvrdik about making a typo helps to resolve this issue. |
To be honest, I was not sure whether it was a typo or not and I was curious if it is something real or not. But the only reason I came up with was easiness to use with jQuery's $.get/$.post. No bashing. |
I am not sure what typo are u talking about... if @JanTvrdik meant that "Nette requires it..." there is no point to continue with that discussion... So what about make this real (documented) feature?Why join only the What about to join the parameters always and remove This is IMHO the way to be more HTTP method independent. What do u think? |
That this is not related to forms at all ;-) |
Maybe ;) But some opinions may be valuable :) |
When u try to send an form via AJAX with the field named the same as a persistent parameter, application will try to save that value to the persistent state although the form has been sent by the POST method and it's fields have NOTHING to do with the persistent state.
Interesting is that within normal POST (non AJAX) this is not happening.
Workaround is to name those fields with some different names.
The text was updated successfully, but these errors were encountered: