topic Re: ajax4jsf and HTML5 - problem rerender HTML5 with xmlparser in Nuxeo Forum

ajax4jsf and HTML5 - problem rerender HTML5 with xmlparser

AlexandreBlanch — Tue, 30 Oct 2012 12:19:44 GMT

I use Nuxeo 5.5 and I develop a front-office using HTML5, JSF and Seam.

When HTML5 tags are in a4j:outputPanel like this

<b>< section>
	< div> test < /div>
< /section></b>

</a4j:outputPanel>

The HTML5 structure is broken like this. Even worse, two sections appear!

< section>< /section> < div>< section>test< /section>< /div>

I found the context parameter below for web.xml, and now the HTML5 structure is respected, but my question is, can i have a potential problem with pages developed by Nuxeo using ajax4jsf ? Thank you!

< context-param>

< param-name>org.ajax4jsf.xmlparser.ORDER< /param-name>
< param-value>NONE< /param-value>

< /context-param>

Re: ajax4jsf and HTML5 - problem rerender HTML5 with xmlparser

AlexandreBlanch — Wed, 31 Oct 2012 14:33:27 GMT

OK, after investigation my best solution is to use NEKO and not NONE and to isolate the context with this configuration:

<context-param>
	<param-name>org.ajax4jsf.xmlparser.ORDER</param-name>
	<param-value>NEKO,TIDY</param-value>
</context-param>
	
<context-param>
	<param-name>org.ajax4jsf.xmlparser.NEKO</param-name>
	<param-value>[path of your web files]</param-value>
</context-param>

But if you find better, I will be very happy to read you! 🙂

Re: ajax4jsf and HTML5 - problem rerender HTML5 with xmlparser

Anahide_Tchertc — Wed, 31 Oct 2012 22:00:47 GMT

That looks like a bug with the default "tidy" parser. This can also happen when using invalid HTML or ajax re-rendering sub elements of tables for instance.