Comments on: Firefox 4k XML node limit

By: Chaitanya

Chaitanya — Thu, 05 Aug 2010 08:18:22 +0000

Thank you. Really helpful.

By: Júlio

Júlio — Thu, 01 Apr 2010 18:17:20 +0000

Thank you very much!!!!!!!!!!!

By: Hsien

Hsien — Wed, 17 Mar 2010 05:45:37 +0000

> I hope I’ve saved someone some pain!
You did again.
Thanks!!

By: Ben

Ben — Tue, 16 Mar 2010 17:38:26 +0000

Hi John,

As far as I know Firefox has always behaved this way. It’s an annoying when you first come across it, but fortunately it isn’t too hard to work around!

Cheers, Ben

By: John (London)

John (London) — Tue, 16 Mar 2010 12:23:08 +0000

Did Firefox always do this?

Anyway, I only just noticed it, so thanks for the easy-to-find solution!

By: Lisa

Lisa — Tue, 20 Oct 2009 03:13:51 +0000

After battling for some while with a fairly complex AJAX app, I thought I was in the home stretch, when – BAM! – I hit this problem with Firefox. I had diagnosed this to the point of realizing there was 4K truncation, and that it happened only in FF and not in IE. However, I had no idea what to do about this and tried a desperate Google search. Fortunately, I came up with your page right away, and I quickly added the fix to my code. It works perfectly.

Thank you very, very much!

By: Jose

Jose — Tue, 13 Oct 2009 15:07:53 +0000

thx.

By: Nelson

Nelson — Thu, 17 Sep 2009 21:32:53 +0000

Thanks man!
We just found out about this issue. Something was parsing good in IE and Firefox when suddenly, as data was growing, it no longer worked right in Firefox…how can it be than our hero browser doesn’t work anymore while IE still does?

Now we just created a function similar to yours to get the text properly.

Thanks dude!

By: romero

romero — Thu, 16 Jul 2009 12:06:08 +0000

Thanks to you! Nice tip!

By: Langdon

Langdon — Fri, 10 Jul 2009 07:29:03 +0000

Thanks Mate.
You really saved my project!
If you’re ever downunder. The beers are on me!