AJAX and forms
I have some forms that interact with the server using AJAX for real reasons: cascading combos, offers, multiple correlated choices (for example, I own {{{{{{{{{{{{{{{{{{ {{{}}} {[Add] ...). I also have some regular fields that I process.
The thing is, once I connected to the server side, it would be easier for me to push all the data that way. It is too far? How about if I have no reason for AJAX and am still using it to enter form data? I would feel obligated to provide a fallback for people with javascript disabled, but the bulk of the logic would be the same, so it isn't a seam to me as much of the overhead. This is kind of data that I would be missing anyway, so I don't lose out on parameters that would be good for something.
Any reason not to do this?
source to share
User experience is an important part of any software product. If you can improve the experience by providing better engagement, there is no reason not to.
Make sure you write unobtrusive and degradable javascript so that users with screen programs or browsers with javascript disabled may end the interaction.
source to share
The only problem with this strategy is that you are experiencing a much deeper problem if someone decides that they want a non-javascript solution. I think it's wise to use the "least fantastic" mechanism that will get the desired result on the Internet. If it's just a post in a form then save it as a post unless there is no reason to do so.
source to share