Hi there,

It's not a problem from Kid, you would have the same result with XSLT. The
problem comes from the way the browser will render XHTML (which is XML)
regarding the content-type you set. It should be application/xhtml+xml but it's
not because Internet Explorer can't deal with it and thus we are stuck with
text/html which is dumb.

The same problem occurs if you try to have several <script /> elements in the
head element. If you close them with /> the browser will not understand you are
closing them and thus the first one will be interpreted but not the other ones.

So:

<script type="text/javascript" src="a.js" />
<script type="text/javascript" src="b.js" />
<script type="text/javascript" src="c.js" />

The browser will not see the closing tags and thus will not load b and c.

Regarding your problem you can simply add an extra space top your textarea like
this:

<textarea name="content"> </textarea>

Therefore the browser will display correctly the form and the texterea will have
a useless space.

Regarding the script elements above you'd need to do:

<script type="text/javascript" src="a.js"> </script>
<script type="text/javascript" src="b.js"> </script>
<script type="text/javascript" src="c.js"> </script>

And it would work just fine.

XHTML is great but almost useless if one can't use the proper content type with
it. Since Microsoft won't support application/xhtml+xml in IE7 we are doomed
for quite a while I'm afraid.

Hope this helped.
- Sylvain

Selon "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>:

>
> Hi all
>
> I trying changing the output of kid templates to XHTML. And I've got a
> problem when trying to render an XHTML form with a textarea field.
>
> The .kid file renders well if accessed directly throught the browser.
> However when I access the same template through TG, the textarea will
> contain the code (XHTML) for the following fields of the form. And the
> followinf fields of the forms aren't displayed.
>
> Could this be a bug in the kid outputting XHTML? Also I noted that the
> XHTML tags are displayed in upper case. Although this is pretty
> straighforward to change, shouldn't it be lower case instead?
>
> Thanx
>
> MarcosM
>
>




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Reply via email to