At the risk of jumping into a conversation that's a little beyond me,
I'd like to throw in 2 cents as a long time jquery user.
I can follow the arguments being made by those who think attr is
broken. But I agree with John and company that the attr function does
what it's supposed to do. It
wrote:
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 marco.rog...@gmail.com wrote:
Sure that's always an option. But the point of the toolkit is to take
advantage of functions that have been tried
20, 7:05 pm, Markw65 mark...@gmail.com wrote:
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 marco.rog...@gmail.com wrote:
I just realized that while this is a compatible
This is essentially a proposal for an enhancement to the two named
functions:
I ran into an issue today when sending parameters with the ajax
function. If the data option is set, $.param is used to encode and
format the keys and values into a query string. But some of the
values in my data were
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 marco.rog...@gmail.com wrote
