I do all my testing on firefox on linux -- no issues. The page info
suggests html:

Type: text/html
Render Mode: Standards compliance mode
Cace Source: Not cached
Encoding: ISO-8859-1
...

-Andrew

On 8/28/06, "R. Müller" <[EMAIL PROTECTED]> wrote:
for it doesn't work, especially in firefox 1.5. the inline-script is not
parsed and executed, if the javascript is marked as comment. what is the
right behavior from specification point of view.

can someone confirm this ?

@andrew : can you check, whether firefox interprets you pages as xhtml
by viewing the side-information. is it following the standard or is it
in quirks-mode ?


regards

ronald

Andrew Robinson wrote:
> I haven't had any issue with the tomahawk components and AJAX/xhtml.
> I'm not so sure of the sandbox. I only had problems with my own code
> when I didn't add the CDATA blocks. Somehow the comment technique is
> working just fine with the tomahawk code.
>
> Here is a snippet from my HTML source as a result of t:popup:
>
> <script type="text/javascript"><!--
> var zfpForm_3AmessagesPopupCompPopup=new
> orgApacheMyfacesPopup('zfpForm:messagesPopupComp',-5,-5);
> //--></script>
>
> FYI, all my pages have this at the top:
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"; ><html
> xmlns="http://www.w3.org/1999/xhtml";>
>
> Any my XHTML pages (facelets) look like:
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
> <html
>  xmlns="http://www.w3.org/1999/xhtml";
>  xmlns:t="http://myfaces.apache.org/tomahawk";
>  xmlns:ui="http://java.sun.com/jsf/facelets";
>  xmlns:h="http://java.sun.com/jsf/html";
>  xmlns:f="http://java.sun.com/jsf/core";
>  xmlns:aa="http://ajaxanywhere.sourceforge.net/";
>  xmlns:fn="http://java.sun.com/jsp/jstl/functions";>
>
>
> Neither AjaxAnywhere or Firefox/IE have an issue with this. My page is
> declared as XHTML and it also loaded through XML & AjaxAnywhere so
> both view it as valid XML.
>
> I'm afraid I don't know anything about SVG to know if there are
> further restrictions
>

Reply via email to