I am very found of GCComment which is highly useful for solving mystery by keeping track of our searches.
However, doing so for very complex mystery caches can lead to text that exceed 4kb (4096) characters.
The GCComment import code from XML (for Dropbox use) fails with such TextNode content too big (XML file from dropbox contains the right data but parser fails to load full data).
I have performed some testing with debug on my big cache's comment.
With your code unmodified, and the following logs:
function parseXMLImport() {
...
if (comments[i].childNodes[3].childNodes[0]) {
var node = comments[i].childNodes[3].childNodes[0];
var nodeValue = node.nodeValue;
console.debug(nodeValue.length);
...
}
I am very found of GCComment which is highly useful for solving mystery by keeping track of our searches. However, doing so for very complex mystery caches can lead to text that exceed 4kb (4096) characters. The GCComment import code from XML (for Dropbox use) fails with such TextNode content too big (XML file from dropbox contains the right data but parser fails to load full data).
I have performed some testing with debug on my big cache's comment. With your code unmodified, and the following logs:
I got the following output in my Firebug
I have searched a bit over the web and found the
textContent
property but it didn't work better with my FF 38.0.5 so I still kept looking over the net and finally found on that forum comment: http://bytes.com/topic/net/answers/482760-problem-reading-large-amount-data-xml-tag#post1866941 So I added the following code:and it begun to work well with the following log output
Hope you will be able to fix that quickly. I have not tested the addition of this code in other browsers but it seems to be part of the standard.