[ http://issues.apache.org/jira/browse/COCOON-556?page=all ]

Jörn Nettingsmeier reopened COCOON-556:
---------------------------------------

             
the problem seems to be that firefox and other browsers do not play nice with 
empty <script/> tags when in "strict" or "standards compliant" mode. as 
described before, firefox will incorrectly parse everything after an emtpy 
<script/> up to the next closing </script>.

the problems in reproducing are probably caused by the reviewer not using 
namespaced xhtml output (which, strangely enough, puts browsers in quirks mode 
where they behave).

a slightly ugly but effective workaround is to add a unicode non-breaking space 
to keep the xslt transformer from collapsing the <script/> elements. i will 
attach a patch.


> incorrect script tags in xhtml (and missing newlines)
> -----------------------------------------------------
>
>                 Key: COCOON-556
>                 URL: http://issues.apache.org/jira/browse/COCOON-556
>             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
>
> 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: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to