It's probably 'parsererror', not 'parseerror', right?
If you search the jQuery source for 'parsererror', you will find the two
places where that error can be thrown. That may shed a little light on it.
Actually what I would do would be to start stripping down the JSON response
until the error goes away. When it starts working (or at least parses OK),
then you know the error was in the part you just removed.
Your JSON data certainly *looks* OK, and it passes the validator at
www.jsonlint.com, but there must be something in it making IE6/7 unhappy. It
works OK in IE8, right?
-Mike
On Tue, Dec 8, 2009 at 11:48 PM, elpatator <romain.simi...@gmail.com> wrote:
> Dear all,
> as suggested above, I just made a quick test using
> error: function(XMLHttpRequest, textStatus, errorThrown)
> {
> alert("XMLHttpRequest: " + XMLHttpRequest);
> alert("textStatus: " + textStatus);
> alert("errorThrown: " + errorThrown);
> },
>
> Wich, in IE6/7, returns me "textStatus:parseerror". What the hell ?
>
