Beside telling people to use a string, the obvious solution would be
to call toString on whatever the function receives. I suppose it could
be possible to parse the result to see if it is a real string or not.
Does anyone know if something like this is cross browser:
var obj = {id: 1, name: 'Ted
Yeah, that's pretty much exactly it. Not entirely sure how we're going
to get around this - this issue has cropped up twice now, with Ajax.
--John
On 8/27/07, Theodore Ni <[EMAIL PROTECTED]> wrote:
>
> I have not looked at the code in depth, but I know that 1.1.4 supports
> recursive $.extend(),
I have not looked at the code in depth, but I know that 1.1.4 supports
recursive $.extend(), which might look at the fields inside your
document.location object and return something the function was not
expecting.
On 8/27/07, drew <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I've been using $.ajax
3 matches
Mail list logo
