[
https://issues.apache.org/jira/browse/TAPESTRY-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509907
]
Bastian Voigt commented on TAPESTRY-961:
----------------------------------------
Can someone please please please commit my fix to the repository??? It is so
annoying having to add the fix manually to each new release of tapestry
Please! Come on, you know that the new XHR api is not yet good enough to
replace XTile in all use cases!
> 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, 4.1.1, 4.1.2
> Environment: FireFox 1.5 browser, Firefox 2.0 browser
> Reporter: Paul Field
> Assignee: 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
