I inherited this app and I'm still getting familiar with all of the
functionality and where all the data is coming from. Many of the ajax
calls went through a central function and I recently updated that
function to use $.ajax instead of the previous custom method. The
problem is that data from a
Marco, why not just sanitize your data, as you use it, to guarantee
that it's not url-encoded?
- Ben
On Nov 23, 10:19 am, Marco Rogers wrote:
> Sure that's always an option. But the point of the toolkit is to take
> advantage of functions that have been tried tested and improved by
> many peopl
Sure that's always an option. But the point of the toolkit is to take
advantage of functions that have been tried tested and improved by
many people. For instance, I'm sure my version wouldn't include the
nice recursive array handling that seems to be baked in to $.param for
1.4.
:Marco
On Nov
You can encode the data yourself, and pass it in as a string (rather
than as key/value pairs).
Then its just used as is...
Mark
On Nov 20, 2:36 pm, Marco Rogers wrote:
> I just realized that while this is a compatible change for $.ajax,
> it's not for $.param. If encodeData isn't passed in, it
I just realized that while this is a compatible change for $.ajax,
it's not for $.param. If encodeData isn't passed in, it'll stop
encoding by default. Gonna put some more thought into it. I'm open
to suggestions.
:Marco
On Nov 20, 5:22 pm, Marco Rogers wrote:
> This is essentially a proposal
