|
After a little more fiddling, I found out
that the problem occurs because of the extra id attribute in the example below.
The tacos:Dialog component adds its own id attribute, so the resulting source
element has two id attributes. I believe that’s what was tripping up the
client-side _javascript_. But I’m not sure why the second version worked. Maybe
the id attribute should be reserved for tacos components like this one? Jeremy From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeremy I’ve run into this in two separate situations now. I have an AjaxDirectLink updating a part with some simple
content in it. In the most recent instance: <div id="myDialog"
jwcid="[EMAIL PROTECTED]:Dialog" hidden="ognl:hidden" > When the client tries to render this part after the request,
it chokes. The entire page goes white and I see the following string
“]>” on a single line and then some gobbly-gook related to the
rest of the content in the part. The fix in both cases has been to move around some of the
attributes in some offending html element within the part. In this case, all I
had to do was change the above to the following: <div id="myDialog"
hidden="ognl:hidden" jwcid="[EMAIL PROTECTED]:Dialog" > It seems that the client-side code parsing the Has anyone else experienced this? It’s a trivial fix,
but very time consuming to diagnose exactly where the offending codes is. Jeremy |
- [Tacos-devel] wierd client-side parsing issue Jeremy
- RE: [Tacos-devel] wierd client-side parsing issue Jeremy
