cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörn Nettingsmeier (JIRA) <>
Subject [jira] Commented: (COCOON-556) incorrect script tags in xhtml (and missing newlines)
Date Fri, 13 Oct 2006 13:58:11 GMT
    [ ] 
Jörn Nettingsmeier commented on COCOON-556:

ok. in order to serve xhtml that also uses the correct xhtml namespace, one needs to apply
post-processing anyways, since iiuc the cforms sheets produce tags without a ns.

> incorrect script tags in xhtml (and missing newlines)
> -----------------------------------------------------
>                 Key: COCOON-556
>                 URL:
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core
>    Affects Versions: 2.0.5-dev (Current CVS)
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Ralf Hauser
>         Assigned To: Cocoon Developers Team
>         Attachments: cforms-avoid_empty_script_tags.diff
> When viewing the forrest myprojects sample site with xhtml, but Mozilla (Build
> 2003010808) and MSIE 6 are unable to render it properly.
> The reason appears to be
> <script src="skin/breadcrumbs.js" language="JavaScript" type="text/javascript"
> /> where both browsers mentioned thereafter no longer parse all subsequent code
> until the next </script> is encountered (unfortunately this is only at the very
> end of the page afer the LastModified script.).
> When serializing it as html, proper </script> end tags are used even if the
> script is empty like the above "breadcrumb".
> A further little nuisance is that the xhtml serializers do not add newlines
> while the regular html serializer does. The effect is that view source of
> browsers is almost unreadable and also in emacs, such source is very hard to
> look at when basically all in one line wrapped dozens of times. This, however
> doesn't seem to have impacted the rendering by the browsers.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message