[ http://issues.apache.org/jira/browse/TAPESTRY-961?page=all ]
Jesse Kuhnert resolved TAPESTRY-961.
------------------------------------
Resolution: Won't Fix
Assignee: Jesse Kuhnert
The new client side XHR api doesn't have this problem. Use that one :)
> Large XTile responses not parsed correctly (FireFox 1.5)
> --------------------------------------------------------
>
> Key: TAPESTRY-961
> URL: http://issues.apache.org/jira/browse/TAPESTRY-961
> Project: Tapestry
> Issue Type: Bug
> Components: Contrib
> Affects Versions: 4.0.1
> Environment: FireFox 1.5 browser
> Reporter: Paul Field
> Assigned To: Jesse Kuhnert
>
> I'm returning a large string (approx 7k) from a listener called by the XTile
> component.
> XTile's extractData() function parses the response like this (relevant code
> chopped out):
> if (xml) dataList = xml.getElementsByTagName('sp');
> for (i = 0; i < dataLen; i++) {
> var child = dataList[i].firstChild; // THIS LINE IS
> THE PROBLEM....
> if (child)
> data[i] = child.data;
>
> }
> The parsing code assumes that the returned text will be a single child node
> of the 'sp' element. Unfortunately, the FireFox parser creates multiple text
> nodes (by default a text node is max 4k in size).
> See here for more info:
> http://www.quirksmode.org/bugreports/archives/2004/12/text_node_maxim.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
