You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Bastian Voigt (JIRA)" <de...@tapestry.apache.org> on 2007/04/18 15:06:15 UTC
[jira] Updated: (TAPESTRY-961) Large XTile responses not parsed
correctly (FireFox 1.5)
[ https://issues.apache.org/jira/browse/TAPESTRY-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bastian Voigt updated TAPESTRY-961:
-----------------------------------
Attachment: XTile.script
Fix bug 961 by iterating over all the text nodes instead of using only the first one.
> Large XTile responses not parsed correctly (FireFox 1.5)
> --------------------------------------------------------
>
> Key: TAPESTRY-961
> URL: https://issues.apache.org/jira/browse/TAPESTRY-961
> Project: Tapestry
> Issue Type: Bug
> Components: Contrib
> Affects Versions: 4.0.2
> Environment: FireFox 1.5 browser
> Reporter: Paul Field
> Assigned To: Jesse Kuhnert
> Attachments: XTile.script
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org