AJAX field with the same name as persistent parameter behaves unpredictible about forms

[JanTvrdik]

That's because in AJAX requires Nette does not differentiate between POST a GET parameters.

[rostenkowski]

Who requires it? Whether it is AJAX or not is irrelevant, isn't it? POST data should be separated from query string parameters.

[Majkl578]

This is an issue of nette/application, not nette/forms, see here.

@JanTvrdik: Is that in some RFC or something?

[rostenkowski]

@JanTvrdik I can't find any material about joining GET and POST parameters in AJAX. Can u please provide some link?

[fprochazka]

@rostenkowski Application/UI/Presenter.php

[Majkl578]

@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.

[fprochazka]

@Majkl578 that was most likely typo and I don't see how bashing @JanTvrdik about making a typo helps to resolve this issue.

[Majkl578]

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.

[rostenkowski]

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 GET and the POST parameters and only in AJAX?

What about to join the parameters always and remove Request::getPost() method? We have no getPut() neither getDelete() methods.

This is IMHO the way to be more HTTP method independent.

What do u think?

[xificurk]

What do u think?

That this is not related to forms at all ;-)

[rostenkowski]

Maybe ;) But some opinions may be valuable :)