Jesse,
You seem to be the expert. Im snagged yet again by IE. The character this
time is & raquo; . In the ajax response its a valid html entity. I added
the space here to make it clearer. Again all browsers are fine with it
except for IE. All characters encoded in the 100's range fails too. There
has to be a way to let IE be more lenient or some trick im missing in
tapestry. This has to be a common error.
Thanks in Advance.
LT
For others having issues with Asyn Responses. Here are some tips.
Guidelines to doing tapestry ASYNC requests in IE and Firefox:
* Repsonse must be valid xml (this means nowraps attributes have to be
nowrap="nowrap" and br tags need to be xhtml compliant. like < br /> (no
spaces of course)
* Comment tags are not allowed (IE only)
* All characters must be encoded or escaped, Check for &'s. 99.9
percent of the time there seems to be an & in some url thats not escaped.
If your not seeing the html updated after the response is received:
* CHECK ALL ABOVE
* In IE you cannot update a ROW <TR> within the dom, this is Illegal.
You must update the table or a div or a td
lt wrote:
>
> In rendering a response from an async request, my html comes back valid.
> All browsers work but IE. I have narrowed it down to special characters
> such as & reg;. Without those IE works. With characters like that, the
> component doesn't update. There has to be a fix for this. My page has a
> valid dtd. (transitional)
>
> Pleas let me know what I can do to fix this.
>
> Thanks.
> L
>
>
>
--
View this message in context:
http://www.nabble.com/Ajax-Response-in-IE-with-HTML-Entities-%284.1.6%29-tp19788294p19957088.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
